[jira] [Commented] (FLINK-32320) Same correlate can not be reused due to the different correlationId

[ https://issues.apache.org/jira/browse/FLINK-32320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17731876#comment-17731876 ] Benchao Li commented on FLINK-32320: [~aitozi] Then you need to open dedicated Calcite issue, and

[jira] [Commented] (FLINK-32320) Same correlate can not be reused due to the different correlationId

[ https://issues.apache.org/jira/browse/FLINK-32320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17731832#comment-17731832 ] Aitozi commented on FLINK-32320: [~libenchao] Thanks for your attention. I just made a quick fix on

[jira] [Commented] (FLINK-32320) Same correlate can not be reused due to the different correlationId

[ https://issues.apache.org/jira/browse/FLINK-32320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17731829#comment-17731829 ] Benchao Li commented on FLINK-32320: You are correct, this will miss some opportunity of reusing

[jira] [Commented] (FLINK-32320) Same correlate can not be reused due to the different correlationId

[ https://issues.apache.org/jira/browse/FLINK-32320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17731823#comment-17731823 ] Aitozi commented on FLINK-32320: In production, multi sink job are very common, if the table from UDTF