hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-17089) make acid 2.0 the default
Date Sat, 12 Aug 2017 19:49:01 GMT


Hive QA commented on HIVE-17089:

Here are the results of testing the latest attachment:

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

{color:red}ERROR:{color} -1 due to 12 failed/errored test(s), 10968 tests executed
*Failed tests:*
org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver[explainanalyze_2] (batchId=100) (batchId=264)
org.apache.hive.hcatalog.api.TestHCatClient.testPartitionRegistrationWithCustomSchema (batchId=180)
org.apache.hive.hcatalog.api.TestHCatClient.testTableSchemaPropagation (batchId=180)

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.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 12 tests failed

This message is automatically generated.

ATTACHMENT ID: 12881612 - PreCommit-HIVE-Build

> make acid 2.0 the default
> -------------------------
>                 Key: HIVE-17089
>                 URL:
>             Project: Hive
>          Issue Type: New Feature
>          Components: Transactions
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>         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
> 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