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

Leonard Xu updated FLINK-22764:
-------------------------------
    Description: 
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.

 

 

  was:
The `Values` source node may be produced in streaming plan optimization by 
`FlinkPruneEmptyRules` currently,  and the `Values` source will be soon to 
`FINISHED` status 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 
job to make the job do checkpoint/savepoint normally, for above situation we 
can throw an exception.

 

 


> 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: Major
>              Labels: stale-major
>
> 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.3.4#803005)

Reply via email to