[
https://issues.apache.org/jira/browse/FLINK-22764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351084#comment-17351084
]
Andy commented on FLINK-22764:
------------------------------
[~Leonard Xu] I think it's not a good solution because of the following reasons:
1. The same problem also exists in a job which contains a regular bounded
source.
2. It's not a better experience for use to get an exception than cannot do
checkpoint and savepoint after `Value`source is finished.
Maybe we could wait for
[FLIP-147|[https://cwiki.apache.org/confluence/display/FLINK/FLIP-147%3A+Support+Checkpoints+After+Tasks+Finished]]
to solve the checkpoints problems after task finished.
> 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
>
> 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.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
