HIVE-29440: [hiveACIDRepl] Add dumpIDs to skipped items LOAD/DUMP items#6296
Open
shivaom02 wants to merge 1 commit intoapache:masterfrom
Open
HIVE-29440: [hiveACIDRepl] Add dumpIDs to skipped items LOAD/DUMP items#6296shivaom02 wants to merge 1 commit intoapache:masterfrom
shivaom02 wants to merge 1 commit intoapache:masterfrom
Conversation
* Details: * After a successful DUMP, all the subsequent LOAD/DUMP which are skipped, should have the DUMP execution id. * Even the LOAD which runs while the DUMP is running should have this DUMP execution id, dues to which the LOAD was skipped. * This helps us identify a full DUMP -> LOAD cycle.
asf-ci-hive
added
tests failed
tests pending
and removed
tests pending
tests failed
labels
|
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
3 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.
What changes were proposed in this pull request?
Why are the changes needed?
So that we can identify a full replication cycle.
Does this PR introduce any user-facing change?
No.
How was this patch tested?