[
https://issues.apache.org/jira/browse/IMPALA-14102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18059354#comment-18059354
]
ASF subversion and git services commented on IMPALA-14102:
----------------------------------------------------------
Commit 090875b02605810358b842d9cc6936026e868736 in impala's branch
refs/heads/master from Steve Carlin
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=090875b02 ]
IMPALA-14102: [part 3] Modified LoptOptimizeJoinRule with Impala changes
The first cut of LoptOptimizeJoinRule class was imported from
Calcite 1.37. This had not been used yet but served as a base for
future Impala changes on this class.
This commit provides the changes that are needed for the rule to
allow Impala specific join optimization code. The rule name has
been changed to ImpalaLoptOptimizeJoinRule to underscore that
this is Impala specific code.
There are some basic name changes of variables, methods,
configurations that were changed. There are two main changes
with this commit.
1) The swapInputs() method compares cost models to decide if
the build side should be swapped with the probe side. The
Calcite version only looks at top level row counts, but this
produced some less optimal plans.
2) The CumulativeCost handler is overridden to factor in that
scan costs need to rely on only the columns fetched from the
scan, not all of the columns.
Testing: Tpcds queries have been changed. Some JUnit tests have been
added as well.
Change-Id: I168ae903934c5c74520a22605e73f71dc0a9d549
Reviewed-on: http://gerrit.cloudera.org:8080/23924
Tested-by: Impala Public Jenkins <[email protected]>
Reviewed-by: Steve Carlin <[email protected]>
> Calcite planner: Customize LoptOptimizeJoinRule
> -----------------------------------------------
>
> Key: IMPALA-14102
> URL: https://issues.apache.org/jira/browse/IMPALA-14102
> Project: IMPALA
> Issue Type: Sub-task
> Reporter: Steve Carlin
> Assignee: Steve Carlin
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
