hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-16785) Ensure replication actions are idempotent if any series of events are applied again.
Date Wed, 21 Jun 2017 17:37:00 GMT


Hive QA commented on HIVE-16785:

Here are the results of testing the latest attachment:

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

{color:red}ERROR:{color} -1 due to 16 failed/errored test(s), 10829 tests executed
*Failed tests:*
org.apache.hadoop.hive.cli.TestBeeLineDriver.testCliDriver[create_merge_compressed] (batchId=237)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[tez_smb_main] (batchId=149)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[vector_if_expr] (batchId=145)
org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver[explainuser_3] (batchId=98)
org.apache.hadoop.hive.cli.TestPerfCliDriver.testCliDriver[query14] (batchId=232)
org.apache.hadoop.hive.cli.TestPerfCliDriver.testCliDriver[query16] (batchId=232)
org.apache.hadoop.hive.cli.TestPerfCliDriver.testCliDriver[query23] (batchId=232)
org.apache.hadoop.hive.cli.TestPerfCliDriver.testCliDriver[query94] (batchId=232)
org.apache.hive.hcatalog.api.TestHCatClient.testPartitionRegistrationWithCustomSchema (batchId=177)
org.apache.hive.hcatalog.api.TestHCatClient.testTableSchemaPropagation (batchId=177)
org.apache.hive.jdbc.TestJdbcWithMiniHS2.testHttpRetryOnServerIdleTimeout (batchId=226)

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: 16 tests failed

This message is automatically generated.

ATTACHMENT ID: 12873893 - PreCommit-HIVE-Build

> Ensure replication actions are idempotent if any series of events are applied again.
> ------------------------------------------------------------------------------------
>                 Key: HIVE-16785
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Hive, repl
>    Affects Versions: 2.1.0
>            Reporter: Sankar Hariappan
>            Assignee: Sankar Hariappan
>              Labels: DR, replication
>             Fix For: 3.0.0
>         Attachments: HIVE-16785.01.patch, HIVE-16785.02.patch, HIVE-16785.03.patch, HIVE-16785.04.patch,
> Some of the events(ALTER, RENAME, TRUNCATE) are not idempotent and hence leads to failure
of REPL LOAD if applied twice or applied on an object which is latest than current event.
For example, if TRUNCATE is applied on a table which is already dropped will fail instead
of noop.
> Also, need to consider the scenario where the object is missing while applying an event.
For example, if RENAME_TABLE event is applied on target where the old table is missing should
validate if table should be recreated or should treat the event as noop. This can be done
by verifying the DB level last repl ID against the current event ID.

This message was sent by Atlassian JIRA

View raw message