[
https://issues.apache.org/jira/browse/HIVE-12017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15013394#comment-15013394
]
Jesus Camacho Rodriguez commented on HIVE-12017:
------------------------------------------------
Thanks a lot [~ashutoshc].
{quote}
-
auto_sortmerge_join_6.q,join42.q,join_star.q,mergejoins_mixed.q,ppd_outer_join5.q,
llap/dynamic_partition_pruning.q : seems like we are generating sub-optimal
plan now.
{quote}
Still exploring each case one by one; I will update the JIRA issue again asap.
{quote}
- wrong results : mergejoin.q
{quote}
New results are right, while previous results were wrong... I have created
HIVE-12465 to track this issue; we can continue the discussion about it over
there.
{quote}
- dynamic_partition_pruning_2.q,hybridgrace_hashjoin_1.q : Hybrid GH Join got
turned off.
{quote}
This is expected. In both cases, inner join is on the equality of constant
values, so it is normal that we get a cartesian product instead of a join.
> Do not disable CBO by default when number of joins in a query is equal or
> less than 1
> -------------------------------------------------------------------------------------
>
> Key: HIVE-12017
> URL: https://issues.apache.org/jira/browse/HIVE-12017
> Project: Hive
> Issue Type: Improvement
> Components: CBO
> Affects Versions: 2.0.0
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
> Attachments: HIVE-12017.01.patch, HIVE-12017.02.patch,
> HIVE-12017.03.patch, HIVE-12017.04.patch, HIVE-12017.05.patch,
> HIVE-12017.06.patch, HIVE-12017.07.patch, HIVE-12017.08.patch,
> HIVE-12017.09.patch, HIVE-12017.10.patch, HIVE-12017.11.patch,
> HIVE-12017.12.patch
>
>
> Instead, we could disable some parts of CBO that are not relevant if the
> query contains 1 or 0 joins. Implementation should be able to define easily
> other query patterns for which we might disable some parts of CBO (in case we
> want to do it in the future).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
