Fixed PrimaryTerm/SeqNo datatypes in UpdateQuery #3137
Merged
Conversation
This file contains hidden or 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
Signed-off-by: Anton Buz <buzdalkin.a@vlprojects.pro>
TheHett
force-pushed
the
gh3136-fix-primary-term-datatype
branch
from
37ccc8e to
fa8c714
Compare
spring-projects-issues
added
the
status: waiting-for-triage
|
Thank you for the PR (and finding that inconsistency). There are two small additional changes - which I will address in a follow up commit:
|
|
@sothawo Thanks! |
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.
Fixed incorrect datatype of
primaryTerm/seqNofields in UpdateQuery (just changed Int -> Long)I did not find similar cases in other classes.
Closes #3136