[Question] Why do we have a SemiTransactionalHiveMetastore in the Hive Connector? #15025
Unanswered
dingqiaoyi
asked this question in
Q&A
Replies: 1 comment 1 reply
-
|
@martint Do you know the history? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Because it tries to simulate transactions by maintaining a list of actions and compensation actions to be performed. Each action may require different metastore operation so transactionality cannot be guaranteed hence it's "Semi-tramsactional". |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Why do we name the HiveMetastore with a prefix 'Semi' as SemiTransactionalHiveMetastore ?
Is it because that we have the Hive connector with partial transactional support, for example lacking in concurrency control, although atomicity seems to be satisfied ?
Beta Was this translation helpful? Give feedback.
All reactions