Hi Gabor,
Thanks for the proposal! However, I find it a little strange. Are you
saying the user can set the operator uid but then doesn't know what they
set when debugging? Otherwise, is the `OperatorIdentifier.forUid("my-uid")`
feasible? I understand your point about potential cross-team work, but the
person may not be able to debug code that was not written by them. Things
get complex in this scenario. Could you provide more details about the
issue you are facing?
Regarding the checkpoint, it is not designed to be self-contained or
human-readable. I suggest not introducing such columns for debugging
purposes.
Best,
Zakelly
On Wed, Aug 7, 2024 at 10:07 PM Gabor Somogyi <gabor.g.somo...@gmail.com>
wrote:
> Hi Devs,
>
> I would like to start a discussion on FLIP-474: Store operator name and UID
> in state metadata[1].
>
> In short users are interested in what kind of operators are inside a
> checkpoint data which can be enhanced from user experience perspective. The
> details can be found in FLIP-474[1].
>
> Please share your thoughts on this.
>
> [1]
>
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-474%3A+Store+operator+name+and+UID+in+state+metadata
>
> BR,
> G
>
