[
https://issues.apache.org/jira/browse/BEAM-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212090#comment-15212090
]
Davor Bonaci commented on BEAM-147:
-----------------------------------
I'd like to push back a little bit against this issue.
The problem with the Aggregator API is that it is unclear where we want to take
this -- there are many paths, and relatively little consensus. Once we finalize
that, we should have a discussion about the proper name. For now, we seem to be
trying to find a descriptive name for something that we don't yet know what it
is or what it is going to be. This doesn't sound like the right way to go;
and/or we'll find ourselves in a situation where the name no longer describes
the concept well enough.
Robert, what do you think? I wouldn't touch this for the time being, let
Aggregators evolve in its own right.
> Rename Aggregator to [P]Metric
> ------------------------------
>
> Key: BEAM-147
> URL: https://issues.apache.org/jira/browse/BEAM-147
> Project: Beam
> Issue Type: Bug
> Components: beam-model, sdk-java-core, sdk-py
> Reporter: Robert Bradshaw
> Assignee: Frances Perry
>
> The name "Aggregator" is confusing.
> See discussion at
> http://mail-archives.apache.org/mod_mbox/incubator-beam-user/201603.mbox/browser
> and
> http://mail-archives.apache.org/mod_mbox/incubator-beam-dev/201603.mbox/browser
> . Exact name still being bikeshedded.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
