[WIP] HIVE-29242: Add catalog for transaction module#6400
Draft
Neer393 wants to merge 1 commit intoapache:masterfrom
Draft
[WIP] HIVE-29242: Add catalog for transaction module#6400Neer393 wants to merge 1 commit intoapache:masterfrom
Neer393 wants to merge 1 commit intoapache:masterfrom
Conversation
Neer393
force-pushed
the
HIVE-29242
branch
2 times, most recently
from
c65d726 to
5f7a473
Compare
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
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.
What changes were proposed in this pull request?
This PR is to add catalog support for transaction module. The following changes were done
hive_metastore.thriftobjects with an optional catalog field which is defaulted to the default catalog when not passed.Why are the changes needed?
This is a new support for making transactions catalog aware. If not done, transactions on same db and table name but in different catalogs could not be differentiated and may show random behaviour.
Does this PR introduce any user-facing change?
No user facing change.
How was this patch tested?
Still work in progress. So testing is yet to be done