[
https://issues.apache.org/jira/browse/FLINK-15556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17014800#comment-17014800
]
Jingsong Lee commented on FLINK-15556:
--------------------------------------
Hi [~godfreyhe], Yes, as you said, sometimes reusing sources will save more
resources than push projects down, and sometimes push projects down will save
more resources than reusing sources. So this switch looks reasonable?
BTW, what is the kind of TableSource? Is it not the same source that can reuse?
> Add a switch for PushProjectIntoTableSourceScanRule
> ---------------------------------------------------
>
> Key: FLINK-15556
> URL: https://issues.apache.org/jira/browse/FLINK-15556
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
> Affects Versions: 1.10.0
> Reporter: hailong wang
> Priority: Minor
> Fix For: 1.11.0
>
>
> In some case, For the project push down, The digest of tableSource maybe
> different. For example, If we create a jdbc tablesource, and is used twice
> after it for different column, the source can not be reused for the different
> digest. In this case, the query io will more precious, So we can add a switch
> to turn off project push down, and the reused the source.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
