hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-17420) bootstrap - get replid before object dump
Date Fri, 01 Sep 2017 07:54:00 GMT


Hive QA commented on HIVE-17420:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 8 failed/errored test(s), 11009 tests executed
*Failed tests:*
TestTxnCommandsBase - did not produce a TEST-*.xml file (likely timed out) (batchId=280)
org.apache.hadoop.hive.cli.TestPerfCliDriver.testCliDriver[query14] (batchId=234)
org.apache.hadoop.hive.cli.TestPerfCliDriver.testCliDriver[query23] (batchId=234)
org.apache.hadoop.hive.ql.lockmgr.TestDbTxnManager2.testMetastoreTablesCleanup (batchId=282)
org.apache.hive.jdbc.TestJdbcWithMiniHS2.testHttpRetryOnServerIdleTimeout (batchId=227)

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

This message is automatically generated.

ATTACHMENT ID: 12884832 - PreCommit-HIVE-Build

> bootstrap - get replid before object dump
> -----------------------------------------
>                 Key: HIVE-17420
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>    Affects Versions: 3.0.0
>            Reporter: anishek
>            Assignee: anishek
>             Fix For: 3.0.0
>         Attachments: HIVE-17420.1.patch, HIVE-17420.2.patch
> when we do the bootstrap dump, the idea is that we take note of the replication id of
a object (table in case of this bug) and then request the table metadata from the rdbms which
is then serialized to _metadata file for the table containing lastReplicationId + table metadata.
> This is to make sure that we only apply events after the event id in _metadata on the
table, which implies that its best to order the call to get currentReplicationId and tablemetadata
retrieval in the event of multiple concurrent operations happening on the same table along
with bootstrap.

This message was sent by Atlassian JIRA

View raw message