Re: [DISCUSS][2.0] Deprecating Accumulator in favor of MetricsGroup

2023-09-01 Thread Matthias Pohl
Thanks for the input. David is right: Beam is also utilizing the accumulators [1]. In this sense you're right that this would require a more wide-spread discussion whether other users would be affected as well. I will give it a bit more thoughts. [1]

Re: [DISCUSS][2.0] Deprecating Accumulator in favor of MetricsGroup

2023-08-28 Thread David Morávek
AFAIK Apache Beam also used acummulators for metric collection, which is indeed a major use case. I’m not convinced that MetricGroup is fuĺly replacing what acummulators have to offer though; OperatorCoordinators might be able to rplace remaining capabilities, but this need bit more thoughts, the

Re: [DISCUSS][2.0] Deprecating Accumulator in favor of MetricsGroup

2023-08-28 Thread Xintong Song
Thanks for bringing this up, Matthias. One thing that a user may achieve with an accumulator but not with a metric group is to programmatically fetch the job execution result, rather than outputting the results to an external sink, in attached mode. This can also be achieved by using CollectSink,

[DISCUSS][2.0] Deprecating Accumulator in favor of MetricsGroup

2023-08-23 Thread Matthias Pohl
Hi everyone, I was looking into serializing the ArchivedExecutionGraph for another FLIP and came across Accumulators [1] (don't mix that one up with the window accumulators of the Table/SQL API). Accumulators were introduced in Flink quite a while ago in Statosphere PR #340 [2]. I had a brief