[
https://issues.apache.org/jira/browse/FLINK-25932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17495479#comment-17495479
]
Wenlong Lyu commented on FLINK-25932:
-------------------------------------
[~slinkydeveloper] when the sql is not changed, most of the sql can be
recompiled with the plan not changed across releases, and users can reload
state from savepoints when upgrading. for example, a simple insert: `insert
into result select sum(price) from history group by user_id`
but now, all of the state is not compatible because all operators are assigned
with a uid.
> 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)
