[jira] [Comment Edited] (HIVE-18619) Verification of temporary Micromanaged table atomicity is needed

["Steve Yeom (JIRA)" <ji...@apache.org>]

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

Steve Yeom edited comment on HIVE-18619 at 2/13/18 10:20 PM:
-------------------------------------------------------------

Using the flag by Eugene we can roll back a transaction in the local TxnManager instance inside the Driver (as Hadoop and Metastore client) 
in a JUnit based unit test. 
The same basic scenario I mentioned 5 days ago works fine. 
Each reader from SELECT gets ValidTxnList that includes aborted transaction id so as to figure out aborted delta directories.
I will add a simple test as a patch for this jira.

Gopal mentioned we need to delete the global transaction entries for the temporary table commands which are left over after Hive-18192 is checked in.
The current IMetaStoreClient implementation for temporary table, 
SessionHiveMetaStoreClient, extends HiveMetaStoreClient and so rollback() method to update 
the MetaStore DB is there but whether the state of the transaction is in the place call that 
function in the state machine is questionable. 



was (Author: steveyeom2017):
Using the flag by Eugene we can roll back a transaction in the local TxnManager instance inside the Driver (as Hadoop and Metastore client) 
in a JUnit based unit test. 
The same basic scenario I mentioned 5 days ago works fine. 
Each reader from SELECT gets ValidTxnList that includes aborted transaction id so as to figure out aborted delta directories.
I will add a simple test as a patch for this jira.

Gopal mentioned we need to delete the global transaction entries for the temporary table commands which are left over after Hive-18192 is checked in.
The current IMetaStoreClient implementation for temporary table does not have rollback() method to update the MetaStore DB.


> Verification of temporary Micromanaged table atomicity is needed 
> -----------------------------------------------------------------
>
>                 Key: HIVE-18619
>                 URL: https://issues.apache.org/jira/browse/HIVE-18619
>             Project: Hive
>          Issue Type: Bug
>          Components: Transactions
>    Affects Versions: 3.0.0
>            Reporter: Steve Yeom
>            Assignee: Steve Yeom
>            Priority: Major
>         Attachments: HIVE-18619.01.patch
>
>
> Session based temporary table by HIVE-7090 had no consideration of Micromanaged table 
> (MM) since there was no insert-only ACID table at its creation tije. 
> HIVE-18599 addressed the issue of no writes during CTTAS (Create Temporary Table As Select)
> on Micro-Managed table. But atomicity of temporary MM table is not verified. 



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