[
https://issues.apache.org/jira/browse/FLINK-23917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Walther closed FLINK-23917.
--------------------------------
Fix Version/s: 1.15.0
1.14.0
Resolution: Fixed
Fixed in master: 73230f70d2a2f9f371703c7f7f36bd91d8633661
Fixed in 1.14: 6d592d5984c1b202838f267a889850445ca844ce
> Project metadata columns to apply to sources which do not implement
> projection pushdown
> ---------------------------------------------------------------------------------------
>
> Key: FLINK-23917
> URL: https://issues.apache.org/jira/browse/FLINK-23917
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
> Reporter: Ingo Bürk
> Assignee: Ingo Bürk
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0, 1.15.0
>
>
> If a source implements SupportsReadingMetadata, but not
> SupportsProjectionPushDown, #applyReadableMetadata is always called with all
> metadata keys declared in the table's schema. If SupportsProjectionPushDown
> is implemented, this is filtered down to only the required metadata keys.
> This can be a problem since metadata could be expensive to calculate.
> The root cause for this is that the projection happens in
> PushProjectIntoTableSourceScanRule which doesn't run for sources which do not
> implement projection pushdown. We should add a new separate rule which
> projects required metadata keys for the source in this case.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
