[jira] [Updated] (FLINK-22764) Disable Values Source node in streaming plan optimization

["Flink Jira Bot (Jira)" <ji...@apache.org>]

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

Flink Jira Bot updated FLINK-22764:
-----------------------------------
    Labels: auto-deprioritized-major stale-minor  (was: auto-deprioritized-major)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> Disable Values Source node in streaming plan optimization
> ---------------------------------------------------------
>
>                 Key: FLINK-22764
>                 URL: https://issues.apache.org/jira/browse/FLINK-22764
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / Planner
>    Affects Versions: 1.13.0
>            Reporter: Leonard Xu
>            Priority: Minor
>              Labels: auto-deprioritized-major, stale-minor
>
> The *Values Source* node may be produced in streaming sql plan optimization by *FlinkPruneEmptyRules* currently,  and the *Values Source* will become *FINISHED* status very soon (the data is bounded) which will lead to the whole job can not do checkpoint and savepoint.
> I think we can add an option to enable/disable values source input in streaming sql job to make the job do checkpoint/savepoint normally, in the other hand we can also throw better exception when a *Values Source* node because many values source node is produced by wrong sql.
>  
>  



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