Hi, after some investigation, here is the final findings:
1. The job accumulator, which represents 1 value accumulated across all
tasks, does show up in the job history file.
lniu@foo:~$ jq . d9830732259de77a04958f4f8ac40a76 | grep
user-task-accumulators
"json":
"{\"job-accumulators\":[],\"
Hi Lu Niu,
Your scenario must be same with me.
I'm so glad to share my solution with you.
1. use the operator state for save the custom statistics data,
2. save the data to external storage when the operator is closing.
3. query from external storage, and make some reduce operation with the data
Thanks Jiadong!
Could you elaborate more? I use application mode to run job in yarn, and
the yarn application will shutdown right after the flink batch job completed
Best
Lu
On Mon, Apr 28, 2025 at 6:49 PM archzi lu wrote:
> hi, Lu Niu
>
> As a workaround, you could use the following ways to
hi, Lu Niu
As a workaround, you could use the following ways to get the custom
accumulator you defined.
1. RestCluserClient#getAccumulators method
2. /jobs/:jobid/accumulators Rest API
Best.
Jiadong Lu
Lu Niu 于2025年4月29日周二 00:41写道：
>
> I am currently running a Flink job in batch mode and usin
