You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2017/03/01 00:18:45 UTC

[jira] [Commented] (HIVE-16063) instead of explicitly specifying mmWriteId during compilation phase, it should only be generated whenever needed during runtime

    [ https://issues.apache.org/jira/browse/HIVE-16063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889178#comment-15889178 ] 

Sergey Shelukhin commented on HIVE-16063:
-----------------------------------------

By generated do you mean retrieved from config, like txn ID? execution cannot talk to metastore.

> instead of explicitly specifying mmWriteId during compilation phase, it should only be generated whenever needed during runtime
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-16063
>                 URL: https://issues.apache.org/jira/browse/HIVE-16063
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Wei Zheng
>            Assignee: Wei Zheng
>
> For ACID transaction logic to work with mm table, first thing is to make the ID usage logic consistent. ACID stores valid txn list in VALID_TXNS_KEY.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)