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 "Owen O'Malley (JIRA)" <ji...@apache.org> on 2008/05/02 00:42:55 UTC

[jira] Updated: (HADOOP-1915) adding counters methods using String (as opposed to Enum)

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

Owen O'Malley updated HADOOP-1915:
----------------------------------

    Status: Open  (was: Patch Available)

I'm sorry for canceling this patch again, but it seems like it really should include a test that calls the new code.

> adding counters methods using String (as opposed to Enum)
> ---------------------------------------------------------
>
>                 Key: HADOOP-1915
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1915
>             Project: Hadoop Core
>          Issue Type: New Feature
>         Environment: all
>            Reporter: Alejandro Abdelnur
>            Assignee: Tom White
>            Priority: Minor
>             Fix For: 0.18.0
>
>         Attachments: hadoop-1915-v2.patch, hadoop-1915-v3.patch, hadoop-1915-v4.patch, hadoop-1915-v5.patch, hadoop-1915-v6.patch, hadoop-1915-v7.patch, hadoop-1915-v8.patch, hadoop-1915-v9.patch, hadoop-1915.patch
>
>
> Currently to use the counters from within Map/Reduce code Enums have to be used, the Enum class defines the group and the Enum itself the counter. Internally they are converted to Strings (the class name and the enum toString) and you can retrieve them as strings from the client API.
> Using dynamic counters (driven by configuration of the map/reduce) is not easy with the counters Enum based API. For example, currently I have an Enum class with 50 enums and we have to map the cardinality to the counter name on the client. This is cumbersome.
> This could be easily improve by adding a String based counter method increment(String group, String counter, long count) to allow use of the counters without Enums.
> Internally this method already exists, so the changes are minimal.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.