[
https://issues.apache.org/jira/browse/FLINK-25932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17495392#comment-17495392
]
Wenlong Lyu commented on FLINK-25932:
-------------------------------------
hi, [~twalthr] [~slinkydeveloper] we may need to have an option to fall back
not to set uids by default. All of the jobs would be state incompatible when
users upgrade to 1.15 with the new uids.
> 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)
