Fix for records that are too large by reducing the bulk update size #796
Conversation
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
…or OpenSearch (Some items had thousands or more authors that ballooned the size recently)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See #792 for problems with some modified records deposited in the last few weeks. They had thousands of authors or more and I guess EZID hasn't seen records of this size until now.
I don't know how to test this really anywhere but production since the other environments don't contain the huge records.
But I manually modified the page size on production and verified it makes the error go away. Script called like.
I have a copy in
~/tmp/ezidso it could be checked out and pulled there and run there without affecting the production deployment.