link.apache.org
> Subject: Re: [DISCUSS] FLIP-395: Deprecate Global Aggregator Manager
>
> +1 for the idea.
>
> Currently OperatorCoordinator is still marked as @Internal, shouldn't
> it be a public API already?
>
> Besides, GlobalAggregatorManager supports coordination betw
users.
I'm also ccing the email to Piotr and David for their suggestions on this.
Best,
Zhanghao Chen
From: Benchao Li
Sent: Monday, November 27, 2023 13:03
To: dev@flink.apache.org
Subject: Re: [DISCUSS] FLIP-395: Deprecate Global Aggregator Manager
+1 fo
+1 for the idea.
Currently OperatorCoordinator is still marked as @Internal, shouldn't
it be a public API already?
Besides, GlobalAggregatorManager supports coordination between
different operators, but OperatorCoordinator only supports
coordination within one operator. And CoordinatorStore intro
Thanks Zhanghao for driving this FLIP.
+1 for this.
Best,
Weihua
On Mon, Nov 20, 2023 at 5:49 PM Zhanghao Chen
wrote:
> Hi all,
>
> I'd like to start a discussion of FLIP-395: Deprecate Global Aggregator
> Manager [1].
>
> Global Aggregate Manager was introduced in [2] to support event time
>
Hi all,
I'd like to start a discussion of FLIP-395: Deprecate Global Aggregator Manager
[1].
Global Aggregate Manager was introduced in [2] to support event time
synchronization across sources and more generally, coordination of parallel
tasks. AFAIK, this was only used in the Kinesis source f
