[
https://issues.apache.org/jira/browse/HIVE-19739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16514878#comment-16514878
]
Hive QA commented on HIVE-19739:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12927830/HIVE-19739.01-branch-3.patch
{color:green}SUCCESS:{color} +1 due to 2 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 9 failed/errored test(s), 14344 tests
executed
*Failed tests:*
{noformat}
TestBeeLineDriver - did not produce a TEST-*.xml file (likely timed out)
(batchId=256)
TestDummy - did not produce a TEST-*.xml file (likely timed out) (batchId=256)
TestMiniDruidCliDriver - did not produce a TEST-*.xml file (likely timed out)
(batchId=256)
TestMiniDruidKafkaCliDriver - did not produce a TEST-*.xml file (likely timed
out) (batchId=256)
TestTezPerfCliDriver - did not produce a TEST-*.xml file (likely timed out)
(batchId=256)
org.apache.hadoop.hive.ql.TestWarehouseExternalDir.testManagedPaths
(batchId=233)
org.apache.hive.jdbc.TestJdbcGenericUDTFGetSplits.testGenericUDTFOrderBySplitCount1
(batchId=242)
org.apache.hive.service.TestHS2ImpersonationWithRemoteMS.testImpersonation
(batchId=242)
org.apache.hive.spark.client.rpc.TestRpc.testServerPort (batchId=308)
{noformat}
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/11827/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/11827/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-11827/
Messages:
{noformat}
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: 9 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12927830 - PreCommit-HIVE-Build
> Bootstrap REPL LOAD to use checkpoints to validate and skip the loaded
> data/metadata.
> -------------------------------------------------------------------------------------
>
> Key: HIVE-19739
> URL: https://issues.apache.org/jira/browse/HIVE-19739
> Project: Hive
> Issue Type: Sub-task
> Components: HiveServer2, repl
> Affects Versions: 3.0.0
> Reporter: Sankar Hariappan
> Assignee: Sankar Hariappan
> Priority: Major
> Labels: DR, pull-request-available, replication
> Fix For: 4.0.0
>
> Attachments: HIVE-19739.01-branch-3.patch, HIVE-19739.01.patch,
> HIVE-19739.02.patch, HIVE-19739.03.patch, HIVE-19739.04.patch
>
>
> Currently. bootstrap REPL LOAD have added checkpoint identifiers in
> DB/table/partition object properties once the data/metadata related to the
> object is successfully loaded.
> If the Db exist and is not empty, then currently we are throwing exception.
> But need to support it for the retry scenario after a failure.
> If there is a retry of bootstrap load using the same dump, then instead of
> throwing error, we should check if any of the tables/partitions are
> completely loaded using the checkpoint identifiers. If yes, then skip it or
> else drop/create them again.
> If the bootstrap load is performed using different dump, then it should throw
> exception.
> Allow bootstrap on empty Db only if ckpt property is not set. Also, if
> bootstrap load is completed on the target Db, then shouldn't allow bootstrap
> retry at all.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
