[
https://issues.apache.org/jira/browse/FLINK-25932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17602168#comment-17602168
]
Wei-Che Wei commented on FLINK-25932:
-------------------------------------
Hi [~slinkydeveloper], [~twalthr],
I found that {{ExecNodeContext#generateUid}} relies on id generated by
{{{}generateUid{}}}, which is a singleton.
I have a use case that it will use multi-thread to submit multiple flink jobs
and each thread will create its own {{StreamExecutionEnvironment}} and
{{StreamTableEnvironment}}. I'm wondering if id generator will be deterministic
as well in such use case. what do you think?
> 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.10#820010)
