IQSS / IQSS/dataverse

Issue using S3 Direct Upload, NoSuchMethodError

Open
#7,220 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature: File Upload & Handling Type: Bug User Role: Depositor
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

The following happens when I try to use S3 Direct Upload:
Dataverse: v. 4.20 build develop-02601927b

awscli is installed, config and credentials have been setup correctly.
has region = eu-central-1 in the config

I have configured the following JVM options:
-Ddataverse.files.s3.type=s3
-Ddataverse.files.s3.label=s3
-Ddataverse.files.s3.bucket-name=dv-dev-bucket
-Ddataverse.files.s3.download-redirect=true
-Ddataverse.files.s3.upload-redirect=true

But as soon as i try to select S3 as the upload option for a dataverse or if i try to upload some files i get the following error:
StandardWrapperValve[Faces Servlet]: Servlet.service() for servlet Faces Servlet threw exception java.lang.NoSuchMethodError: com.fasterxml.jackson.databind.ObjectMapper.enable([Lcom/fasterxml/jackson/core/JsonParser$Feature;)Lcom/fasterxml/jackson/databind/ObjectMapper

According to Stackoverflow this seems to be a dependency related issue:

Has anyone else experienced the same problem?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure with the reported Dataverse 4.20 configuration and S3 upload JVM options. Inspect the resolved Java dependencies for conflicting Jackson versions around the ObjectMapper call, then verify that selecting S3 and uploading files no longer raises NoSuchMethodError.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, java
Domain
backend, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.