hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene Koifman (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-19750) Initialize NEXT_WRITE_ID. NWI_NEXT on converting an existing table to full acid
Date Mon, 04 Jun 2018 04:46:00 GMT

     [ https://issues.apache.org/jira/browse/HIVE-19750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Eugene Koifman updated HIVE-19750:
----------------------------------
    Attachment: HIVE-19750.03.patch

> Initialize NEXT_WRITE_ID. NWI_NEXT on converting an existing table to full acid
> -------------------------------------------------------------------------------
>
>                 Key: HIVE-19750
>                 URL: https://issues.apache.org/jira/browse/HIVE-19750
>             Project: Hive
>          Issue Type: Bug
>          Components: Transactions
>    Affects Versions: 3.0.0
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>            Priority: Critical
>             Fix For: 3.1.0
>
>         Attachments: HIVE-19750.01.patch, HIVE-19750.02.patch, HIVE-19750.03.patch
>
>
> Need to set this to a reasonably high value the the table.
> This will reserve a range of write IDs that will be treated by the system as committed.
> This is needed so that we can assign unique ROW__IDs to each row in files that already
exist in the table.  For example, if the value is initialized to the number of files currently
in the table, we can think of each file as written by a separate transaction and thus a free
to assign bucketProperty (BucketCodec) of ROW_ID in whichever way is convenient.
> it's guaranteed that all rows get unique ROW_IDs this way.



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

Mime
View raw message