[
https://issues.apache.org/jira/browse/FLINK-32940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17757992#comment-17757992
]
Jark Wu edited comment on FLINK-32940 at 8/23/23 12:21 PM:
-----------------------------------------------------------
Hi [~vsowrirajan], thank you for reporting this problem. Which Flink version
are you using? And could you share the execution plan of the query by executing
`EXPLAIN` statement on the query?
was (Author: jark):
Hi [~vsowrirajan], thank you for reporting this problem. Which Flink version
are you using?
> Support projection pushdown to table source for column projections through
> UDTF
> -------------------------------------------------------------------------------
>
> Key: FLINK-32940
> URL: https://issues.apache.org/jira/browse/FLINK-32940
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Reporter: Venkata krishnan Sowrirajan
> Priority: Major
>
> Currently, Flink doesn't push down columns projected through UDTF like
> _UNNEST_ to the table source.
> For eg:
> {code:java}
> select t1.name, t2.ename from DEPT_NESTED as t1, unnest(t1.employees) as
> t2{code}
> For the above SQL, Flink projects all the columns for DEPT_NESTED rather than
> only _name_ and {_}employees{_}. If the table source supports nested fields
> column projection, ideally it should project only _t1.employees.ename_ from
> the table source.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
