hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-6439) Introduce CBO step in Semantic Analyzer
Date Sat, 22 Feb 2014 00:30:20 GMT

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

Ashutosh Chauhan commented on HIVE-6439:
----------------------------------------

Is plan to get CBO optimizer work in 0.13 timeframe? If no, I think we may want to delay this
till branching 0.13 Otherwise, this will go in 0.13 release with a config which doesn't do
anything and thus will be confusing for end users.

> Introduce CBO step in Semantic Analyzer
> ---------------------------------------
>
>                 Key: HIVE-6439
>                 URL: https://issues.apache.org/jira/browse/HIVE-6439
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Harish Butani
>            Assignee: Harish Butani
>         Attachments: HIVE-6439.1.patch, HIVE-6439.2.patch, HIVE-6439.4.patch, HIVE-6439.5.patch
>
>
> This patch introduces CBO step in SemanticAnalyzer. For now the CostBasedOptimizer is
an empty shell. 
> The contract between SemAly and CBO is:
> - CBO step  is controlled by the 'hive.enable.cbo.flag'. 
> - When true Hive SemAly will hand CBO a Hive Operator tree (with operators annotated
with stats). If it can CBO will return a better plan in Hive AST form.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message