hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-20531) One of the task , either move or add partition can be avoided in repl load flow
Date Fri, 28 Sep 2018 07:15:00 GMT


Hive QA commented on HIVE-20531:

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 1 failed/errored test(s), 15005 tests executed
*Failed tests:*
TestMiniDruidCliDriver - did not produce a TEST-*.xml file (likely timed out) (batchId=195)

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
Tests exited with: TestsFailedException: 1 tests failed

This message is automatically generated.

ATTACHMENT ID: 12941515 - PreCommit-HIVE-Build

> One of the task , either move or add partition can be avoided in repl load flow
> -------------------------------------------------------------------------------
>                 Key: HIVE-20531
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: repl
>    Affects Versions: 4.0.0
>            Reporter: mahesh kumar behera
>            Assignee: mahesh kumar behera
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>         Attachments: HIVE-20531.01.patch, HIVE-20531.02.patch, HIVE-20531.03.patch, HIVE-20531.04.patch
> In replication load, both add partition and insert operations are handled through import.
Import creates 3 major tasks. Copy, add partition and move. Copy does the copy of data from
source location to staging directory. Then add partition (which runs in parallel to copy)
creates the partition in meta store. Its a no op in case of insert and by the time this ddl
task is executed for insert partition would be already present. The third operation is move.
Which actually moves the file from staging directory to actual location. And then in case
of insert it adds the insert event to notification table. It does this for add partition operation
which is redundant as the event for add partition would have been written already by ddl task.
With the optimization to copy directly to actual table location in S3, move task can be avoided
for add partition operation replay and replay of insert need not create the add partition
(ddl) task.

This message was sent by Atlassian JIRA

View raw message