Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
3.0.0
-
None
Description
Per table write ID implementation (HIVE-18192) have introduced write ID and maps it against the txn.
Now, for streaming ingest, we need to open txns batch and then allocate write id for each txn in the batch which is 2 metastore calls.
This can be optimised to use only one metastore api.
Attachments
Issue Links
- is related to
-
HIVE-18192 Introduce WriteID per table rather than using global transaction ID
- Closed