{
"emoji": "♥️",
"version": 1
}
o ensure
>>>>> cross-version state compatibility. However, this cannot be easily done
>>>>> when
>>>>> setting the uidHash, that's why Flink currently does not support setting
>>>>> it
>>>>> for non-legacy sinks.
>>
rator. Maybe you can further investigate it and fire a JIRA
>>> issue on it.
>>>
>>> Best,
>>> Zhanghao Chen
>>> --
>>> *From:* Salva Alcántara
>>> *Sent:* Sunday, June 9, 2024 14:49
>>> *To:* Ga
te the corresponding uidHash for
>> each suboperator. Maybe you can further investigate it and fire a JIRA
>> issue on it.
>>
>> Best,
>> Zhanghao Chen
>> --
>> *From:* Salva Alcántara
>> *Sent:* Sunday, June 9, 2024 14:49
>> *To:* Gabor
ply the
> same strategy for generating uids to compute the corresponding uidHash for
> each suboperator. Maybe you can further investigate it and fire a JIRA
> issue on it.
>
> Best,
> Zhanghao Chen
> --
> *From:* Salva Alcántara
> *Sent:* Sunday, June
e the corresponding uidHash for each
suboperator. Maybe you can further investigate it and fire a JIRA issue on it.
Best,
Zhanghao Chen
From: Salva Alcántara
Sent: Sunday, June 9, 2024 14:49
To: Gabor Somogyi
Cc: user
Subject: Re: Setting uid hash for non-legacy
Hi Gabor,
Yeah, I know this, but what if you initially forgot and now you want to add
the uid "after the fact"?
You need to get the operator/vertex id used by Flink for current savepoints
and somehow set this id for the sink.
With the uid method you would need to "hack" the existing hash (get a
Hi Salva,
Just wondering why not good to set the uid like this?
```
output.sinkTo(outputSink).uid("my-human-readable-sink-uid");
```
>From the mentioned UID Flink is going to make the hash which is consistent
from UID -> HASH transformation perspective.
BR,
G
On Fri, Jun 7, 2024 at 7:54 AM Sa
