You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Krisztian Kasa (Jira)" <ji...@apache.org> on 2021/04/14 02:55:00 UTC

[jira] [Assigned] (HIVE-25012) Parsing table alias is failing if query has table properties specified

     [ https://issues.apache.org/jira/browse/HIVE-25012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Krisztian Kasa reassigned HIVE-25012:
-------------------------------------


> Parsing table alias is failing if query has table properties specified
> ----------------------------------------------------------------------
>
>                 Key: HIVE-25012
>                 URL: https://issues.apache.org/jira/browse/HIVE-25012
>             Project: Hive
>          Issue Type: Bug
>          Components: CBO, Parser
>            Reporter: Krisztian Kasa
>            Assignee: Krisztian Kasa
>            Priority: Major
>
> {code}
> select t1.ROW__IS__DELETED, t1.*, t2.ROW__IS__DELETED, t2.* from t1('acid.fetch.deleted.rows'='true')
> join t2('acid.fetch.deleted.rows'='true') on t1.a = t2.a;
> {code}
> When creating Join RelNode the aliases are used to lookup left and right input RelNodes. Aliases are extracted from the AST subtree of the left and right inputs of the join AST node. In case of a table reference:
> {code}
> TOK_TABREF
>    TOK_TABNAME
>       t1
>    TOK_TABLEPROPERTIES
>       TOK_TABLEPROPLIST
>          TOK_TABLEPROPERTY
>             'acid.fetch.deleted.rows'
>             'true'
> {code} 
> Prior HIVE-24854 queries mentioned above failed because existing solution was not expect TOK_TABLEPROPERTIES.
> The goal of this patch is to parse TOK_TABREF properly using existing solution also used in SemanticAnalyser.doPhase1



--
This message was sent by Atlassian Jira
(v8.3.4#803005)