[
https://issues.apache.org/jira/browse/HIVE-19708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492193#comment-16492193
]
Hive QA commented on HIVE-19708:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12925111/HIVE-19708.01.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 13 failed/errored test(s), 14287 tests
executed
*Failed tests:*
{noformat}
TestCLIAuthzSessionContext - did not produce a TEST-*.xml file (likely timed
out) (batchId=244)
TestCopyUtils - did not produce a TEST-*.xml file (likely timed out)
(batchId=232)
TestHS2AuthzContext - did not produce a TEST-*.xml file (likely timed out)
(batchId=244)
TestJdbcWithLocalClusterSpark - did not produce a TEST-*.xml file (likely timed
out) (batchId=244)
TestJdbcWithMiniHS2 - did not produce a TEST-*.xml file (likely timed out)
(batchId=244)
TestJdbcWithSQLAuthUDFBlacklist - did not produce a TEST-*.xml file (likely
timed out) (batchId=244)
TestJdbcWithSQLAuthorization - did not produce a TEST-*.xml file (likely timed
out) (batchId=244)
TestMultiSessionsHS2WithLocalClusterSpark - did not produce a TEST-*.xml file
(likely timed out) (batchId=244)
TestNoSaslAuth - did not produce a TEST-*.xml file (likely timed out)
(batchId=244)
TestReplicationOnHDFSEncryptedZones - did not produce a TEST-*.xml file (likely
timed out) (batchId=232)
TestReplicationScenarios - did not produce a TEST-*.xml file (likely timed out)
(batchId=232)
TestReplicationScenariosAcidTables - did not produce a TEST-*.xml file (likely
timed out) (batchId=232)
TestReplicationScenariosAcrossInstances - did not produce a TEST-*.xml file
(likely timed out) (batchId=232)
{noformat}
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/11274/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/11274/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-11274/
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: 13 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12925111 - PreCommit-HIVE-Build
> Repl copy retrying with cm path even if the failure is due to network issue
> ---------------------------------------------------------------------------
>
> Key: HIVE-19708
> URL: https://issues.apache.org/jira/browse/HIVE-19708
> Project: Hive
> Issue Type: Task
> Components: Hive, HiveServer2, repl
> Affects Versions: 3.1.0
> Reporter: mahesh kumar behera
> Assignee: mahesh kumar behera
> Priority: Major
> Fix For: 3.1.0
>
> Attachments: HIVE-19708.01.patch
>
>
> * During repl load
> ** for filesystem based copying of file if the copy fails due to a
> connection error to source Name Node, we should recreate the filesystem
> object.
> ** the retry logic for local file copy should be triggered using the
> original source file path ( and not the CM root path ) since failure can be
> due to network issues between DFSClient and NN.
> * When listing files in tables / partition to include them in _files, we
> should add retry logic when failure occurs. FileSystem object here also
> should be recreated since the existing one might be in inconsistent state.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
