Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-6227

Configuration does not lock parameters marked final if they have no value.

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 0.21.0
    • conf
    • None
    • Reviewed

    Description

      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.

      Attachments

        1. patch-6227-ydist.txt
          3 kB
          Vinod Kumar Vavilapalli
        2. patch-6227-0.20.txt
          2 kB
          Amareshwari Sriramadasu
        3. patch-6227.txt
          3 kB
          Amareshwari Sriramadasu

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            amareshwari Amareshwari Sriramadasu
            yhemanth Hemanth Yamijala
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment