You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Aitozi (Jira)" <ji...@apache.org> on 2022/11/04 03:33:00 UTC

[jira] [Closed] (FLINK-29748) Expose the optimize phase in the connector context

     [ https://issues.apache.org/jira/browse/FLINK-29748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aitozi closed FLINK-29748.
--------------------------
    Resolution: Won't Fix

> Expose the optimize phase in the connector context
> --------------------------------------------------
>
>                 Key: FLINK-29748
>                 URL: https://issues.apache.org/jira/browse/FLINK-29748
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / Planner, Table SQL / Runtime
>            Reporter: Aitozi
>            Priority: Minor
>
> Currently, in the connector it can not know whether the whole optimize is finished.
> When the optimize finished, the all information is static, eg: the reading partitions. If I want to validate the final optimized result (like whether the reading partition is too much or empty), it needs the context of what is the current phase. I think the {{ScanContext}} is ok to expose this information. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)