hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-20699) Query based compactor for full CRUD Acid tables
Date Mon, 04 Feb 2019 22:50:00 GMT


Hive QA commented on HIVE-20699:

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 due to 2 test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 15729 tests passed

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase

This message is automatically generated.

ATTACHMENT ID: 12957535 - PreCommit-HIVE-Build

> Query based compactor for full CRUD Acid tables
> -----------------------------------------------
>                 Key: HIVE-20699
>                 URL:
>             Project: Hive
>          Issue Type: New Feature
>          Components: Transactions
>    Affects Versions: 3.1.0
>            Reporter: Eugene Koifman
>            Assignee: Vaibhav Gumashta
>            Priority: Major
>         Attachments: HIVE-20699.1.patch, HIVE-20699.1.patch, HIVE-20699.10.patch, HIVE-20699.2.patch,
HIVE-20699.3.patch, HIVE-20699.4.patch, HIVE-20699.5.patch, HIVE-20699.6.patch, HIVE-20699.7.patch,
HIVE-20699.8.patch, HIVE-20699.9.patch
> Currently the Acid compactor is implemented as generated MR job ({{}}).
> It could also be expressed as a Hive query that reads from a given partition and writes
data back to the same partition.  This will merge the deltas and 'apply' the delete events.
 The simplest would be to just use Insert Overwrite but that will change all ROW__IDs which
we don't want.
> Need to implement this in a way that preserves ROW__IDs and creates a new {{base_x}}
directory to handle Major compaction.
> Minor compaction will be investigated separately.

This message was sent by Atlassian JIRA

View raw message