flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leonard Xu (Jira)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-22764) Disable Values Source node in streaming plan optimization
Date Fri, 28 May 2021 01:51:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-22764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352922#comment-17352922

Leonard Xu commented on FLINK-22764:

I also know that FLIP-147 is final answer, this issue has existed for long time, my proposal
is just a quick fix in our Company internal.
If all of us agree that we should to wait the FLIP-147 finished, I'm ok to don't fix this
problem in SQL side right away.

> 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

View raw message