[
https://issues.apache.org/jira/browse/HADOOP-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala updated HADOOP-6227:
-------------------------------------
Resolution: Fixed
Fix Version/s: (was: 0.20.1)
0.21.0
Assignee: Amareshwari Sriramadasu
Release Note: Modified configuration to allow setting final parameters
with null values.
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
I just committed this to trunk. Thanks, Amareshwari !
I did not commit to the 0.20 branch, because there's an active vote in progress
and did not think this existing bug should block the release. If decided
otherwise, we can commit to the 0.20 branch as well.
> 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
> Assignee: Amareshwari Sriramadasu
> Fix For: 0.21.0
>
> Attachments: patch-6227-0.20.txt, patch-6227-ydist.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.
