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/27 16:37:00 UTC
[jira] [Work stopped] (HIVE-18750) Exchange partition should be
disabled on ACID/Insert-only tables with per table write ID.
[ https://issues.apache.org/jira/browse/HIVE-18750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on HIVE-18750 stopped by Sankar Hariappan.
-----------------------------------------------
> Exchange partition should be disabled on ACID/Insert-only tables with per table write ID.
> -----------------------------------------------------------------------------------------
>
> Key: HIVE-18750
> URL: https://issues.apache.org/jira/browse/HIVE-18750
> Project: Hive
> Issue Type: Sub-task
> Components: HiveServer2, Transactions
> Affects Versions: 3.0.0
> Reporter: Sankar Hariappan
> Assignee: Sankar Hariappan
> Priority: Major
> Labels: ACID, DDL, pull-request-available
> Fix For: 3.0.0
>
> Attachments: HIVE-18750.01.patch
>
>
> Per table write id implementation (HIVE-18192) have introduced write ID per table and used write ID to name the delta/base files and also as primary key for each row.
> Now, exchange partition have to move delta/base files across tables without changing the write ID which causes incorrect results.
> Also, this exchange partition feature is there to support the use-case of atomic updates. But with ACID updates, we shall support atomic-updates and hence it makes sense to not support exchange partition for ACID and MM tables.
> The qtest file mm_exchangepartition.q test results to be updated after this change.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)