You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Jesus Camacho Rodriguez (JIRA)" <ji...@apache.org> on 2015/08/01 12:06:04 UTC

[jira] [Commented] (HIVE-11397) Parse Hive OR clauses as they are written into the AST

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

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

I checked the code and it shouldn't be that difficult to do... Then we need to explore how to actually exploit it (taking into account the Calcite translation, etc). We could check in this one, and create a bigger patch exploring the multiple inputs idea in HIVE-11398.

> Parse Hive OR clauses as they are written into the AST
> ------------------------------------------------------
>
>                 Key: HIVE-11397
>                 URL: https://issues.apache.org/jira/browse/HIVE-11397
>             Project: Hive
>          Issue Type: Bug
>          Components: Logical Optimizer
>    Affects Versions: 1.3.0, 2.0.0
>            Reporter: Gopal V
>            Assignee: Jesus Camacho Rodriguez
>         Attachments: HIVE-11397.1.patch, HIVE-11397.patch
>
>
> When parsing A OR B OR C, hive converts it into 
> (C OR B) OR A
> instead of turning it into
> A OR (B OR C)
> {code}
>         GenericUDFOPOr or = new GenericUDFOPOr();
>         List<ExprNodeDesc> expressions = new ArrayList<ExprNodeDesc>(2);
>         expressions.add(previous);
>         expressions.add(current);
> {code}



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