You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Vineet Garg (JIRA)" <ji...@apache.org> on 2018/04/09 20:53:04 UTC
[jira] [Updated] (HIVE-18193) Migrate existing ACID tables to use
write id per table rather than global transaction id
[ https://issues.apache.org/jira/browse/HIVE-18193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vineet Garg updated HIVE-18193:
-------------------------------
Fix Version/s: (was: 3.0.0)
3.1.0
Deferring this to 3.1.0 since the branch for 3.0.0 has been cut off. Please update the JIRA if you would like to get your patch in 3.0.0.
> Migrate existing ACID tables to use write id per table rather than global transaction id
> ----------------------------------------------------------------------------------------
>
> Key: HIVE-18193
> URL: https://issues.apache.org/jira/browse/HIVE-18193
> Project: Hive
> Issue Type: Sub-task
> Components: HiveServer2, Transactions
> Affects Versions: 3.0.0
> Reporter: anishek
> Assignee: Sankar Hariappan
> Priority: Major
> Fix For: 3.1.0
>
>
> dependent upon HIVE-18192
> For existing ACID Tables we need to update the table level write id metatables/sequences so any new operations on these tables works seamlessly without any conflicting data in existing base/delta files.
> 1. Need to create metadata tables such as NEXT_WRITE_ID and TXN_TO_WRITE_ID and add entries for each ACID/MM tables.
> 2. All current open transactions to have an entry in TXN_TO_WRITE_ID to avoid allocating multiple write IDs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)