hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene Koifman (JIRA)" <>
Subject [jira] [Updated] (HIVE-17089) make acid 2.0 the default
Date Wed, 16 Aug 2017 01:19:00 GMT


Eugene Koifman updated HIVE-17089:
       Resolution: Fixed
    Fix Version/s: 3.0.0
           Status: Resolved  (was: Patch Available)

patch 16 committed to master
thanks Sergey for the review
cc [~saketj]

> make acid 2.0 the default
> -------------------------
>                 Key: HIVE-17089
>                 URL:
>             Project: Hive
>          Issue Type: New Feature
>          Components: Transactions
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>             Fix For: 3.0.0
>         Attachments: HIVE-17089.01.patch, HIVE-17089.03.patch, HIVE-17089.05.patch, HIVE-17089.06.patch,
HIVE-17089.07.patch, HIVE-17089.10.patch, HIVE-17089.10.patch, HIVE-17089.11.patch, HIVE-17089.12.patch,
HIVE-17089.13.patch, HIVE-17089.14.patch, HIVE-17089.15.patch, HIVE-17089.16.patch
> acid 2.0 is introduced in HIVE-14035.  It replaces Update events with a combination of
Delete + Insert events.  This now makes U=D+I the default (and only) supported acid table
type in Hive 3.0.  
> The expectation for upgrade is that Major compaction has to be run on all acid tables
in the existing Hive cluster and that no new writes to these table take place since the start
of compaction (Need to add a mechanism to put a table in read-only mode - this way it can
still be read while it's being compacted).  Then upgrade to Hive 3.0 can take place.

This message was sent by Atlassian JIRA

View raw message