[
https://issues.apache.org/jira/browse/HIVE-15808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855804#comment-15855804
]
Hive QA commented on HIVE-15808:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12851343/HIVE-15808.5.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 4 failed/errored test(s), 10230 tests
executed
*Failed tests:*
{noformat}
TestDerbyConnector - did not produce a TEST-*.xml file (likely timed out)
(batchId=235)
org.apache.hadoop.hive.cli.TestEncryptedHDFSCliDriver.testCliDriver[encryption_join_with_different_encryption_keys]
(batchId=159)
org.apache.hadoop.hive.cli.TestPerfCliDriver.testCliDriver[query14]
(batchId=223)
org.apache.hadoop.hive.cli.TestPerfCliDriver.testCliDriver[query23]
(batchId=223)
{noformat}
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/3414/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/3414/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-3414/
Messages:
{noformat}
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: 4 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12851343 - PreCommit-HIVE-Build
> Remove semijoin reduction branch if it is on bigtable along with hash join
> --------------------------------------------------------------------------
>
> Key: HIVE-15808
> URL: https://issues.apache.org/jira/browse/HIVE-15808
> Project: Hive
> Issue Type: Bug
> Reporter: Deepak Jaiswal
> Assignee: Deepak Jaiswal
> Attachments: HIVE-15808.2.patch, HIVE-15808.3.patch,
> HIVE-15808.4.patch, HIVE-15808.5.patch, HIVE-15808.patch
>
>
> If there is a semijoin branch on the same operator pipeline which contains a
> hash join then it is by design on big table which is not optimal. The
> operator cycle detection logic may not find a cycle as there is no cycle at
> operator level. However, once Tez builds its task there can be a cycle at
> task level causing the query to fail.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
