hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-20090) Extend creation of semijoin reduction filters to be able to discover new opportunities
Date Sat, 14 Jul 2018 02:05:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-20090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16543948#comment-16543948
] 

Hive QA commented on HIVE-20090:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12931571/HIVE-20090.08.patch

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 14651 tests passed

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/12597/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/12597/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-12597/

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
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12931571 - PreCommit-HIVE-Build

> Extend creation of semijoin reduction filters to be able to discover new opportunities
> --------------------------------------------------------------------------------------
>
>                 Key: HIVE-20090
>                 URL: https://issues.apache.org/jira/browse/HIVE-20090
>             Project: Hive
>          Issue Type: Improvement
>          Components: Physical Optimizer
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Jesus Camacho Rodriguez
>            Priority: Major
>         Attachments: HIVE-20090.01.patch, HIVE-20090.02.patch, HIVE-20090.04.patch, HIVE-20090.05.patch,
HIVE-20090.06.patch, HIVE-20090.07.patch, HIVE-20090.08.patch
>
>
> Assume the following plan:
> {noformat}
> TS[0] - RS[1] - JOIN[4] - RS[5] - JOIN[8] - FS[9]
> TS[2] - RS[3] - JOIN[4] 
> TS[6] - RS[7] - JOIN[8]
> {noformat}
> Currently, {{TS\[6\]}} may only be reduced with the output of {{RS\[5\]}}, i.e., input
to join between both subplans.
> However, it may be useful to consider other possibilities too, e.g., reduced by the output
of {{RS\[1\]}} or {{RS\[3\]}}. For instance, this is important when, given a large plan, an
edge between {{RS[5]}} and {{TS[0]}} would create a cycle, while an edge between {{RS[1]}}
and {{TS[6]}} would not.
> This patch comprises two parts. First, it creates additional predicates when possible.
Secondly, it removes duplicate semijoin reduction branches/predicates, e.g., if another semijoin
that consumes the output of the same expression already reduces a certain table scan operator
(heuristic, since this may not result in most efficient plan in all cases). Ultimately, the
decision on whether to use one or another should be cost-driven (follow-up).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message