release/v20.11: fix(subscriptions): fix subscription to use the kv with the max version#7355
Merged
aman-bansal merged 1 commit intorelease/v20.11from Jan 22, 2021
Merged
Conversation
…on (#7349) Issue: The last KV from the list received from subscription need not be the latest update. This is because of the KVs written at the top due to value log rewrites or due to rollups. We were using the last KV from the updates received via subscription. Fix: Iterate over the KVs to get the KV with the latest version. (cherry picked from commit 4a2bc36)
NamanJain8
requested review from
danielmai,
manishrjain,
pawanrawal and
vvbalaji-dgraph
as code owners
github-actions
Bot
added
the
area/graphql
NamanJain8
changed the title
aman-bansal
approved these changes
Jan 22, 2021
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Issue:
The last KV from the list received from subscription need not be the latest update. This is because of the KVs written at the top due to value log rewrites or due to rollups.
We were using the last KV from the updates received via subscription.
Fix:
Iterate over the KVs to get the KV with the latest version.
(cherry picked from commit 4a2bc36)
This change is