You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Rayman (Jira)" <ji...@apache.org> on 2019/12/12 20:24:00 UTC

[jira] [Updated] (SAMZA-2417) Investigate and move MetricGroup.newGauge to always by default overwrite any existing Gauge if one by the same name is already present.

     [ https://issues.apache.org/jira/browse/SAMZA-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rayman updated SAMZA-2417:
--------------------------
    Description: 
Currently MetricGroup and MetricsRegistry has two separate APIs for newGauge one that simply adds a new gauge if one is not present, and the other that allows overwriting existing Gauge objects. 

This other behavior is desirable in cases where a gauge is recreated, e.g., see [https://github.com/apache/samza/pull/1223]

However, it may be possible to make the overwriting behavior the default and only behavior.

> Investigate and move MetricGroup.newGauge to always by default overwrite any existing Gauge if one by the same name is already present.
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SAMZA-2417
>                 URL: https://issues.apache.org/jira/browse/SAMZA-2417
>             Project: Samza
>          Issue Type: Improvement
>            Reporter: Rayman
>            Priority: Major
>
> Currently MetricGroup and MetricsRegistry has two separate APIs for newGauge one that simply adds a new gauge if one is not present, and the other that allows overwriting existing Gauge objects. 
> This other behavior is desirable in cases where a gauge is recreated, e.g., see [https://github.com/apache/samza/pull/1223]
> However, it may be possible to make the overwriting behavior the default and only behavior.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)