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
DM-40395: Allow datastore record inserts to use ensure or replace #880
Merged
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
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #880 +/- ##
==========================================
- Coverage 87.71% 87.70% -0.01%
==========================================
Files 274 274
Lines 36117 36195 +78
Branches 7553 7575 +22
==========================================
+ Hits 31680 31746 +66
- Misses 3264 3272 +8
- Partials 1173 1177 +4
☔ View full report in Codecov by Sentry. |
timj
force-pushed
the
tickets/DM-40395
branch
2 times, most recently
from
August 17, 2023 19:44
1e18bb7
to
469238c
Compare
andy-slac
approved these changes
Aug 18, 2023
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.
Looks good, a couple of minor questions.
timj
force-pushed
the
tickets/DM-40395
branch
3 times, most recently
from
August 18, 2023 21:05
120c7a2
to
c26b00b
Compare
This should have been done when we removed the support for ingesting unresolved refs.
…uations Until we have a coherent way of handling record clashes, for ingest assume that if UUIDv5 IDs are being used and the file is not going to be transferred into the datastore, then replacing existing records is allowable.
This is a questionable change and needs some further thought, but it is more consistent with what is actually happening and the chances of a disassembled composite and an assembled composite clashing are low.
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.
This doesn't solve the real problem of the files being overwritten without us knowing whether the datastore records are allowed to be modified but it does give the option.
Checklist
doc/changes