[
https://issues.apache.org/jira/browse/FLINK-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15339224#comment-15339224
]
Maximilian Michels commented on FLINK-3757:
-------------------------------------------
Accumulators are first created locally without checking at the JobManager
whether they exist. Only once they have been transferred to the JobManager they
are merged (and errors are reported). Since accumulators can be created at
arbitrary points during job execution, I think this behavior makes sense. We
would have to send a message to the JobManager upon creation or do static
analysis of the code to see if accumulators collide.
I would say it is a feature to avoid making requests to the JobManager during
execution :)
> addAccumulator does not throw Exception on duplicate accumulator name
> ---------------------------------------------------------------------
>
> Key: FLINK-3757
> URL: https://issues.apache.org/jira/browse/FLINK-3757
> Project: Flink
> Issue Type: Bug
> Reporter: Konstantin Knauf
> Priority: Minor
>
> Works if tasks are chained, but in many situations it does not, see
> See https://gist.github.com/knaufk/a0026eff9792aa905a2f586f3b0cb112
> Is this an undocumented feature or a valid bug?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
