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

Sergey Shelukhin commented on HIVE-8395:
----------------------------------------

>From memory... 
For most join tests, the problem is that 3-way join gets split into 2 stages. 
It doesn't happen in all cases and it was decided to investigate later.
constprog2 may be re-enable-able; again non-critical, some particularly obscure 
const propagation does not happen due to plan changes.
Infer_bucket_sort*, optimize_nullscan, subquery_* have changes because they 
depends on particularly crafted plans to test specific scenarios, and  CBO 
changes the plan, should not be an issue.
For list bucketing plans change with CBO, but we decided we don't care, someone 
might need to investigate, it's a rarely if ever used feature.
partition_wise_fileformat2 I don't remember.
ql_rewrite_gbtoidx had hard-to-fix obscure index usage issues (index not used 
for 1 query), deemed not important enough/can be fixed later.
test5.q no idea.

> CBO: enable by default
> ----------------------
>
>                 Key: HIVE-8395
>                 URL: https://issues.apache.org/jira/browse/HIVE-8395
>             Project: Hive
>          Issue Type: Improvement
>          Components: CBO
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>             Fix For: 0.15.0
>
>         Attachments: HIVE-8395.01.patch, HIVE-8395.02.patch, 
> HIVE-8395.03.patch, HIVE-8395.04.patch, HIVE-8395.05.patch, 
> HIVE-8395.06.patch, HIVE-8395.07.patch, HIVE-8395.08.patch, 
> HIVE-8395.09.patch, HIVE-8395.10.patch, HIVE-8395.11.patch, 
> HIVE-8395.12.patch, HIVE-8395.12.patch, HIVE-8395.13.patch, 
> HIVE-8395.13.patch, HIVE-8395.14.patch, HIVE-8395.15.patch, 
> HIVE-8395.16.patch, HIVE-8395.17.patch, HIVE-8395.18.patch, 
> HIVE-8395.18.patch, HIVE-8395.19.patch, HIVE-8395.20.patch, 
> HIVE-8395.21.patch, HIVE-8395.22.patch, HIVE-8395.23.patch, HIVE-8395.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to