[
https://issues.apache.org/jira/browse/FLINK-19639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17213764#comment-17213764
]
Shengkai Fang commented on FLINK-19639:
---------------------------------------
CC [~godfreyhe] [~jark]
> Support SupportsNestedProjectionPushDown in planner
> ---------------------------------------------------
>
> Key: FLINK-19639
> URL: https://issues.apache.org/jira/browse/FLINK-19639
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / Planner
> Reporter: Shengkai Fang
> Priority: Major
>
> Support to push nested projection into {{TableSourceScan}}. But it may cause
> name conflicts in some situaion. For example, we create table with ddl
> {code:sql}
> CREATE TABLE NestedTable (
> nest1 ROW<a INT>,
> nest2 ROW<a INT>
> )
> {code}
> and with query
> {code:sql}
> SELECT nest1.a, nest2.a from NestedTable
> {code}
> and we will get 2 {{`a`}} in the new schema when pushing projection.
> Here we use {{'_'}} to concatenate the names of all levels as the name of
> the nested fields. In this example, we will get fields {{nest1_a, nest2_a}}
> in the new schema.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
