-
Notifications
You must be signed in to change notification settings - Fork 500
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
Released and unchanged datasets appear as new drafts when upgrading from 4.8.6 to 4.9.4 #5142
Comments
@lmaylein that doesn't sound good. Are you basing this on what you're seeing in the database or Solr? |
Phew. I'm already recovering nicely from my heart attack. Could it be that the draft datasets have been around for a long time but never indexed? Perhaps you ran an "index all" as part of your migration process? I long time ago I wrote some code to "diff" what's in Solr vs the database but it's buggy and we haven't documented it. You can find references to it in #4205. |
I've reindexed our 4.8.6 (productive) dataverse now. The number number of dataset is the same as before. The nine additional draft versions don't appear in 4.8.6. If I copy the dataset links generated by 4.9.4 to our official/productive domain
I'll check your diff script. |
Ok. After fixing the problem described in #5141 ... The URL shows the same result, when clicking on the "ghost draft":
|
Additional information: Affected are the last nine datasets which have been released (in 4.8.6). |
Is this helpful in some way? 4.8.6:
4.9.4:
|
Can I further support the debugging of this problem? In the solr result cited, both datasets (draft and release) have the same datasetVersionID. Maybe a problem with a join while indexing? Which, however, speaks aginst it are the old metadata (description "Dummy") which are displayed in the search result for the drafts and which certainly reflects a state before the first release. |
@lmaylein hi, all the detail here is much appreciated but can you please email [email protected] to open a support ticket? If you've done this already, you can just mention the ticket number here. Thanks! |
Mea culpa! If I deploy every version between 4.8.6 and 4.9.4 |
When upgrading form 4.8.6 to 4.9.4 the number of the datasets in our instance is increased.
There are additional draft versions for already publicated (and unchanged) datasets.
The text was updated successfully, but these errors were encountered: