[
https://issues.apache.org/jira/browse/HIVE-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16355885#comment-16355885
]
Steve Yeom commented on HIVE-18619:
-----------------------------------
A possible test case scenario for this jira is:
1. Start a Session
2. CREATE TEMPORARY TABLE mm_tab in MM(Micro-managed).
3. INSERT INTO mm_tab -- SUCCEEDED
4. INSERT INTO mm_tab -- FAILED and should leave the current statement's delta
directory which should be recognized as aborted
5. SELECT FROM mm_tab -- Should only return the data at 3.
This simple test case may verify basic case for atomicity of operations on
TEMPORARY MM table.
The patch for writeId for Replication HIVE-18192 may will affect the behavior
when checked in.
> 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: Minor
>
> 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)
