hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amareshwari Sriramadasu (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-6227) Configuration does not lock parameters marked final if they have no value.
Date Tue, 01 Sep 2009 12:38:33 GMT

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

Amareshwari Sriramadasu updated HADOOP-6227:
--------------------------------------------

    Fix Version/s: 0.20.1
           Status: Patch Available  (was: Open)

> Configuration does not lock parameters marked final if they have no value.
> --------------------------------------------------------------------------
>
>                 Key: HADOOP-6227
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6227
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>            Reporter: Hemanth Yamijala
>             Fix For: 0.20.1
>
>         Attachments: patch-6227-0.20.txt, patch-6227.txt
>
>
> A use-case: Recently, we stumbled on a bug that wanted us to disable the feature to run
a debug script in map/reduce on tasks that fail, specified by mapred.{map|reduce}.task.debug.script.
The best way of disabling it seemed to be to set it with no value in the cluster configuration
and mark it final. This did not work, however, because the code in configuration explicitly
checks if the value is not null before adding it to the list of final parameters.
> Without an ability to do this, there might be a need to explicitly have a special way
of disabling optional features.

-- 
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