[
https://issues.apache.org/jira/browse/FLINK-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923710#comment-15923710
]
ASF GitHub Bot commented on FLINK-3849:
---------------------------------------
Github user KurtYoung commented on the issue:
https://github.com/apache/flink/pull/3520
To address the problem of not reusing `TableSource` when we create a new
scan for table source, i changed some inheritance for current `BatchScan`,
`StreamScan`, `BatchTableSourceScan`, `StreamTableSourceScan` and so on. The
new structure is moe likely as the relationship between `FlinkTable` and
`TableSourceTable`, `DataSetTable`, `DataStreamTable`.
After changing the structure, it also make it possible to unify the push
project into scan rule for both batch and stream mode.
> Add FilterableTableSource interface and translation rule
> --------------------------------------------------------
>
> Key: FLINK-3849
> URL: https://issues.apache.org/jira/browse/FLINK-3849
> Project: Flink
> Issue Type: New Feature
> Components: Table API & SQL
> Reporter: Fabian Hueske
> Assignee: Kurt Young
>
> Add a {{FilterableTableSource}} interface for {{TableSource}} implementations
> which support filter push-down.
> The interface could look as follows
> {code}
> def trait FilterableTableSource {
> // returns unsupported predicate expression
> def setPredicate(predicate: Expression): Expression
> }
> {code}
> In addition we need Calcite rules to push a predicate (or parts of it) into a
> TableScan that refers to a {{FilterableTableSource}}. We might need to tweak
> the cost model as well to push the optimizer in the right direction.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
