[
https://issues.apache.org/jira/browse/CALCITE-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16795090#comment-16795090
]
Rong Rong commented on CALCITE-2906:
------------------------------------
I dont think anything after parser has been implemented. see discussion in
CALCITE-2721.
I think this is just first step to add in the parser support but somehow it
doesn't work that well.
My understanding is we need to regroup some of the parsing logics so that it
can reuse logics in \{{expression2b}}.
> Record DOT extension does not distinguish between simple and compound
> identifiers
> ---------------------------------------------------------------------------------
>
> Key: CALCITE-2906
> URL: https://issues.apache.org/jira/browse/CALCITE-2906
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Rong Rong
> Assignee: Danny Chan
> Priority: Major
>
> Currently the DOT extensions only supports Simple Identifiers:
> For example:
> * *{{tbl.foo(0).col.bar}}* is parsed as: *{{((`TBL`.`FOO`(0).`COL`).`BAR`)}}*
> However, this is not the case in regular Expression field, for example:
> * *{{tbl.col.bar}}* is parsed as: *{{`TBL`.`COL`.`BAR`}}*
> Parser should support both compound identifier, and simple identifier chain
> after a record type SqlNode.
> Similarly, parsing should also be consistent for other types of expression,
> for example
> * *{{tbl.arr[0].foo.bar}}* is currently parsed as:
> *{{((`TBL`.`ARR`[0].`FOO`).`BAR`)}}*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
