-
Notifications
You must be signed in to change notification settings - Fork 493
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
8878 5.11.1 hotfix #8879
Merged
Merged
8878 5.11.1 hotfix #8879
Changes from 13 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
3967820
getEditVersion will create a new version if one doesn't exist
qqmyers 05e026e
fix for file delete
qqmyers 23f84b0
null dataset thumb if being deleted
qqmyers aa2dc36
add null check
qqmyers 277d16c
also clear from new file list
qqmyers 9fac1fd
loop and compare on datafile
qqmyers d50412a
don't loop unless there is a thumb
qqmyers de25eac
test work-around per pdurbin
qqmyers d48f797
add 5.11.1 release notes #8878
pdurbin 1361067
bump version to 5.11.1 #8878
pdurbin f79a954
tweak release notes #8878
pdurbin d463e48
typo in war file name #8878
pdurbin 08ae12b
fix version in sphinx #8878
pdurbin 0f185b5
Update 5.11.1-release-notes.md
landreev File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,72 @@ | ||
# Dataverse Software 5.11.1 | ||
|
||
This is a bug fix release of the Dataverse Software. Dataverse Software v5.11 will no longer be made available and installations should upgrade directly from v5.10.1 to v5.11.1. | ||
|
||
## Release Highlights | ||
|
||
Dataverse Software 5.11 contains two critical issues that are fixed in this release. | ||
|
||
First, if you delete a file from a published version of a dataset that has restricted files, the file will be deleted from the file system (or S3) and lose its "owner id" in the database. For details, see Issue #8867. | ||
|
||
Second, if you are a superuser, it's possible to click "Delete Draft" and delete a published dataset if it has restricted files. For details, see #8845 and #8742. | ||
|
||
## Notes for Dataverse Installation Administrators | ||
|
||
### Identifying Datasets with Deleted Files | ||
|
||
If you have been running 5.11, check if any files show "null" for the owner id. The "owner" of a file is the parent dataset: | ||
|
||
``` | ||
select * from dvobject where dtype = 'DataFile' and owner_id is null; | ||
``` | ||
|
||
For any of these files, change the owner id to the database id of the parent dataset. In addition, the file on disk (or in S3) is likely gone. Look at the "storageidentifier" field from the query above to determine the location of the file then restore the file from backup. | ||
|
||
### Identifying Datasets Superusers May Have Accidentally Destroyed | ||
|
||
Check the "actionlogrecord" table for DestroyDatasetCommand. While these "destroy" entries are normal when a superuser uses the API to destroy datasets, an entry is also created if a superuser has accidentally deleted a published dataset in the web interface with the "Delete Draft" button. | ||
|
||
## Complete List of Changes | ||
|
||
For the complete list of code changes in this release, see the [5.11.1 Milestone](https://github.com/IQSS/dataverse/milestone/105?closed=1) in GitHub. | ||
|
||
For help with upgrading, installing, or general questions please post to the [Dataverse Community Google Group](https://groups.google.com/forum/#!forum/dataverse-community) or email [email protected]. | ||
|
||
## Installation | ||
|
||
If this is a new installation, please see our [Installation Guide](https://guides.dataverse.org/en/5.11.1/installation/). Please also contact us to get added to the [Dataverse Project Map](https://guides.dataverse.org/en/5.11.1/installation/config.html#putting-your-dataverse-installation-on-the-map-at-dataverse-org) if you have not done so already. | ||
|
||
## Upgrade Instructions | ||
|
||
0\. These instructions assume that you've already successfully upgraded from Dataverse Software 4.x to Dataverse Software 5 following the instructions in the [Dataverse Software 5 Release Notes](https://github.com/IQSS/dataverse/releases/tag/v5.0). After upgrading from the 4.x series to 5.0, you should progress through the other 5.x releases before attempting the upgrade to 5.11.1. | ||
|
||
If you are running Payara as a non-root user (and you should be!), **remember not to execute the commands below as root**. Use `sudo` to change to that user first. For example, `sudo -i -u dataverse` if `dataverse` is your dedicated application user. | ||
|
||
In the following commands we assume that Payara 5 is installed in `/usr/local/payara5`. If not, adjust as needed. | ||
|
||
`export PAYARA=/usr/local/payara5` | ||
|
||
(or `setenv PAYARA /usr/local/payara5` if you are using a `csh`-like shell) | ||
|
||
1\. Undeploy the previous version. | ||
|
||
- `$PAYARA/bin/asadmin list-applications` | ||
- `$PAYARA/bin/asadmin undeploy dataverse<-version>` | ||
|
||
2\. Stop Payara and remove the generated directory | ||
|
||
- `service payara stop` | ||
- `rm -rf $PAYARA/glassfish/domains/domain1/generated` | ||
|
||
3\. Start Payara | ||
|
||
- `service payara start` | ||
|
||
4\. Deploy this version. | ||
|
||
- `$PAYARA/bin/asadmin deploy dataverse-5.11.1.war` | ||
|
||
5\. Restart Payara | ||
|
||
- `service payara stop` | ||
- `service payara start` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To upgrade from 5.10.1, follow the instructions for installing release 5.11 using the v5.11.1 war file. If you had previously installed v5.11 (no longer available), follow the simplified instructions below.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great, I'll go ahead and add this. I will also add this sentence/some form thereof to the very top of the release note.