On 12.09.20 17:20, Alexey Trenikhun wrote:
We use union state to generate sequences, each operator generates offset0 +
number-of-tasks - task-index + task-specific-counter * number-of-tasks (e.g.
for 2 instances of operator -one instance produce even number, another odd).
Last generated seque
Subject: Re: [DISCUSS] Deprecate and remove UnionList OperatorState
Generally +1
The one use case I've seen of union state I've seen in production (outside of
sources and sinks) is as a "poor mans" broadcast state. This was obviously
before that feature was added which is now
:* Seth Wiesman
> *Sent:* Wednesday, September 9, 2020 9:37:03 AM
> *To:* dev
> *Cc:* Aljoscha Krettek ; user
> *Subject:* Re: [DISCUSS] Deprecate and remove UnionList OperatorState
>
> Generally +1
>
> The one use case I've seen of union state I've seen in prod
Generally +1
The one use case I've seen of union state I've seen in production (outside
of sources and sinks) is as a "poor mans" broadcast state. This was
obviously before that feature was added which is now a few years ago so I
don't know if those pipelines still exist. FWIW, if they do the stat
+1 to getting rid of non-keyed state as is in general and for union state
in particular. I had a hard time to wrap my head around the semantics of
non-keyed state when designing the rescale of unaligned checkpoint.
The only plausible use cases are legacy source and sinks. Both should also
be rewor
