hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6317) Serialize the 'final'ness of Configuration keys
Date Wed, 21 Oct 2009 17:21:59 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768339#action_12768339
] 

Arun C Murthy commented on HADOOP-6317:
---------------------------------------

I was thinking along the lines of the tasktracker doing something like:

conf.setFinalInt("mapred.task.id", taskAttemptId);
or
conf.setInt("mapred.task.id", taskAttemptId, true);

where we have the necessary apis like so:

Configuration.setFinalInt(String key, int value);
or
Configuration.setInt(String key, int value, boolean finalParam);

Does that make sense?


> Serialize the 'final'ness of Configuration keys
> -----------------------------------------------
>
>                 Key: HADOOP-6317
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6317
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: conf
>            Reporter: Arun C Murthy
>            Assignee: Aaron Kimball
>             Fix For: 0.22.0
>
>         Attachments: HADOOP-6317.patch
>
>
> Currently Configuration.writeXml doesn't serialize the 'final' attribute. There are some
scenarios where it is useful:
> # TaskTracker should mark the tasks' 'localized' parameters as 'final' 
> # GUI tools

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


Mime
View raw message