You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sankar Hariappan (JIRA)" <ji...@apache.org> on 2018/02/20 09:11:00 UTC

[jira] [Updated] (HIVE-18752) HiveEndPoint: Optimise metastore calls to open transactions batch and allocate write Ids.

     [ https://issues.apache.org/jira/browse/HIVE-18752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sankar Hariappan updated HIVE-18752:
------------------------------------
    Summary: HiveEndPoint: Optimise metastore calls to open transactions batch and allocate write Ids.  (was: HiveEndPoint: Optimise opening batch transactions and getting write Ids for each transaction in the batch into single metastore api.)

> HiveEndPoint: Optimise metastore calls to open transactions batch and allocate write Ids.
> -----------------------------------------------------------------------------------------
>
>                 Key: HIVE-18752
>                 URL: https://issues.apache.org/jira/browse/HIVE-18752
>             Project: Hive
>          Issue Type: Sub-task
>          Components: HiveServer2, Metastore
>    Affects Versions: 3.0.0
>            Reporter: Sankar Hariappan
>            Assignee: Sankar Hariappan
>            Priority: Major
>              Labels: ACID, Metastore, Streaming
>             Fix For: 3.0.0
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)