-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in request Dataverse API to report successful upload #38
Comments
Hi @scruz002 - thanks for reporting this; it looks to me like this API may have broken in the multiple file store support for https://github.com/IQSS/dataverse/releases/tag/v4.20. Is it possible for you to check with Dataverse <= 4.19 to see if this error is still present? |
This looks like a missed step in setting up v4.20 - in the v4.20 release upgrade instructions there's a section on updates related to multi-store support, which are required even if you are only using one store. I've copied those instructions below - the ones you need depends on whether you're using a file or S3 store. In either case there are new jvm options to be set in glassfish using the appropriate commands. The following set of commands to change the Glassfish JVM options will adapt an existing file or s3 store for this upgrade:
For a s3 store:
|
Sorry but we have no way to downgrade Dataverse in our homologation environment. Do you know of anyone using DCM in version 4.20? |
We already tried this configuration and got the same error |
Line 1346 is trying to get the storage driver id to use. That can be set by default or per Dataverse (if you have more than one store defined): Is your -Ddataverse.files.storage-driver-id= option set to the id of the store you want to use? (In the examples above that would be 'file' or 's3' but it would have to match whatever storage-id you use.) |
Hi,
I think we're almost making DCM work. The steps to follow
are being performed correctly:
But we are having a problem. After moving files to /hold.
the post_upload.bash script makes a request to the Dataverse API to inform
successful in receiving the files. However, the Dataverse is returning an error.
In the Dataverse log
In the source code of Dataverse version 4.20 (edu.harvard.iq.dataverse.api.Datasets)
Apparently the property "dataverse.file." + storageDriver + ".type" is not defined.
We would like to know how in configuration we can define the appropriate values for
this property so that the request to Dataverse API can be handled correctly.
We noticed that the properties related to the upload folder start with "dataverse.files" and not "dataverse.file".
Thanks for any help.
The text was updated successfully, but these errors were encountered: