hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (Jira)" <>
Subject [jira] [Commented] (HIVE-21213) Acid table bootstrap replication needs to handle directory created by compaction with txn id
Date Sun, 29 Dec 2019 02:59:00 GMT


Hive QA commented on HIVE-21213:

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 17791 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: 12989615 - PreCommit-HIVE-Build

> Acid table bootstrap replication needs to handle directory created by compaction with
txn id
> --------------------------------------------------------------------------------------------
>                 Key: HIVE-21213
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive, HiveServer2, repl
>            Reporter: mahesh kumar behera
>            Assignee: mahesh kumar behera
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HIVE-21213.01.patch, HIVE-21213.02.patch, HIVE-21213.03.patch, HIVE-21213.04.patch,
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
> The current implementation of compaction uses the txn id in the directory name. This
is used to isolate the queries from reading the directory until compaction has finished and
to avoid the compactor marking used earlier. In case of replication, during bootstrap , directory
is copied as it is with the same name from source to destination cluster. But the directory
created by compaction with txn id can not be copied as the txn list at target may be different
from source. The txn id which is valid at source may be an aborted txn at target. So conversion
logic is required to create a new directory with valid txn at target and dump the data to
the newly created directory.

This message was sent by Atlassian Jira

View raw message