[
https://issues.apache.org/jira/browse/HIVE-21537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16805659#comment-16805659
]
Hive QA commented on HIVE-21537:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12964250/HIVE-21537.3.patch
{color:red}ERROR:{color} -1 due to build exiting with an error
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/16771/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/16771/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-16771/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL
https://issues.apache.org/jira/secure/attachment/12964250/HIVE-21537.3.patch
was found in seen patch url's cache and a test was probably run already on it.
Aborting...
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12964250 - PreCommit-HIVE-Build
> Scalar query rewrite could be improved to not generate an extra join if
> subquery is guaranteed to produce atmost one row
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-21537
> URL: https://issues.apache.org/jira/browse/HIVE-21537
> Project: Hive
> Issue Type: Improvement
> Components: Query Planning
> Affects Versions: 4.0.0
> Reporter: Vineet Garg
> Assignee: Vineet Garg
> Priority: Major
> Labels: sub-query
> Attachments: HIVE-21537.1.patch, HIVE-21537.2.patch,
> HIVE-21537.3.patch
>
>
> Currently Hive planner introduces this branch and later executes a rule to
> remove this branch if it could.
> Subquery remove rule itself could check if subquery will produce max one row
> (using relmetadat's getMaxRowCount) and avoid introducing this branch.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
