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

Configuration no longer sets all keys in a deprecated key list.

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • 0.23.3, 0.24.0
    • 0.23.3, 2.0.2-alpha
    • conf
    • None

    Description

      I did not look at the patch for HADOOP-8167 previously, but I did in response to a recent test failure. The patch appears to have changed the following code (I am just paraphrasing the code)

      if(!deprecated(key)) {
        set(key, value);
      } else {
        for(String newKey: depricatedKeyMap.get(key)) {
          set(newKey, value);
        }
      }
      

      to be

      set(key, value);
      if(depricatedKeyMap.contains(key)) {
         set(deprecatedKeyMap.get(key)[0], value);
      } else if(reverseKeyMap.contains(key)) {
         set(reverseKeyMap.get(key), value);
      }
      

      If a key is deprecated and is mapped to more then one new key value only the first one in the list will be set, where as previously all of them would be set.

      Attachments

        Issue Links

        Activity

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

          People

            anupamseth Anupam Seth Assign to me
            revans2 Robert Joseph Evans
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment