[
https://issues.apache.org/jira/browse/FLINK-25932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17495455#comment-17495455
]
Francesco Guardiani commented on FLINK-25932:
---------------------------------------------
Hi [~wenlong.lwl], I don't understand how an option would help you. All the
jobs are already state incompatible these days between minor releases, as the
plan changes and the json plan. Even if you were using the json plan from 1.14,
as we modified heavily its shape, you won't be able to load it in 1.15.
Can you be more specific on which use cases, possibly with examples, do you
have in mind?
> Introduce ExecNodeContext.generateUid()
> ---------------------------------------
>
> Key: FLINK-25932
> URL: https://issues.apache.org/jira/browse/FLINK-25932
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Planner
> Reporter: Timo Walther
> Assignee: Francesco Guardiani
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> FLINK-25387 introduced an {{ExecNodeContext}} which contains all information
> to generate unique and deterministic identifiers for all created
> {{Transformation}}.
> This issue includes:
> - Add {{ExecNodeContext.generateUid(operatorName: String): String}}
> - Go through all ExecNodes and give transformations a uid. The name can be
> constant static field within the ExecNode such that both annotation and
> method can use it.
> - We give all transformations a uid, including stateless ones.
> - The final UID should look like:
> {{13_stream-exec-sink_1_upsert-materializer}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
