You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Raghu Angadi (JIRA)" <ji...@apache.org> on 2007/01/12 23:12:27 UTC
[jira] Commented: (HADOOP-887) metrics API should enforce some
restrictions on tag and metric names
[ https://issues.apache.org/jira/browse/HADOOP-887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464369 ]
Raghu Angadi commented on HADOOP-887:
-------------------------------------
and '.'? datanode.reads, datanode.writes is more human friendly than namenode_reads and consistent with hadoop config names.
> metrics API should enforce some restrictions on tag and metric names
> --------------------------------------------------------------------
>
> Key: HADOOP-887
> URL: https://issues.apache.org/jira/browse/HADOOP-887
> Project: Hadoop
> Issue Type: Improvement
> Components: metrics
> Affects Versions: 0.10.1
> Reporter: Nigel Daley
> Priority: Minor
>
> The metrics API currently allows any string to be a metric name or tag name (see org.apache.hadoop.metrics.Metrics.createRecord(...) and org.apache.hadoop.metrics .Metrics.report(...)).
> Such unrestricted names makes it difficult to implement metrics providers that generate source code to manipulate these metrics, since many characters are invalid as method or variable names.
> I'd like to propose that metric names be restricted to letters, digits, and underscore (A-Za-z0-9_) and this restriction be documented and enforced by the API.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira