You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Francesco Guardiani (Jira)" <ji...@apache.org> on 2022/04/11 15:47:00 UTC

[jira] [Commented] (FLINK-24700) Clarify semantics of filter, projection, partition, and metadata pushdown

    [ https://issues.apache.org/jira/browse/FLINK-24700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17520654#comment-17520654 ] 

Francesco Guardiani commented on FLINK-24700:
---------------------------------------------

Has this one already been solved [~twalthr] by one of the previous interfaces reworking efforts?

> Clarify semantics of filter, projection, partition, and metadata pushdown
> -------------------------------------------------------------------------
>
>                 Key: FLINK-24700
>                 URL: https://issues.apache.org/jira/browse/FLINK-24700
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / API
>            Reporter: Timo Walther
>            Assignee: Timo Walther
>            Priority: Major
>
> FLINK-19903 has revealed a couple of shortcomings that occur when implementing multiple ability interfaces. We should improve the documentation and better define the semantics.
> - Push produced type not only for metadata pushdown but also projection push down.
> - Clarify order of filter + projection
> - Clarify order of projection/filter + partition
> - Simplify handling of partition columns
> ...



--
This message was sent by Atlassian Jira
(v8.20.1#820001)