hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesus Camacho Rodriguez (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-9200) CBO (Calcite Return Path): Inlining data structures of ParseContext in Join operator
Date Tue, 23 Dec 2014 19:45:13 GMT

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

Jesus Camacho Rodriguez commented on HIVE-9200:
-----------------------------------------------

[~jpullokkaran], I attach a RB link, can you check it? I just want to know if we are on the
same page.
In particular, I have inlined the QBJoinTree object; however, I kept _joinContext_, _mapJoinContext_,
_smbMapJoinContext_ in the ParseContext as Sets, as there are optimizations in Hive that use
these structures to iterate over e.g. all the map joins in a query. Should we definitively
get rid of them in the ParseContext?
The second question concerns SemanticAnalyzer, as you said you do not want to change anything
there. As I changed the data structures in ParseContext, I changed them accordingly in SemanticAnalyzer.
Can you check it? Which do you think is the right way to approach this?
Thanks.

> CBO (Calcite Return Path): Inlining data structures of ParseContext in Join operator
> ------------------------------------------------------------------------------------
>
>                 Key: HIVE-9200
>                 URL: https://issues.apache.org/jira/browse/HIVE-9200
>             Project: Hive
>          Issue Type: Sub-task
>          Components: CBO
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Jesus Camacho Rodriguez
>             Fix For: 0.15.0
>
>




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

Mime
View raw message