Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.0
    • Component/s: None
    • Labels:
      None

      Description

      Now that there's OAuth support, it's possible to have a notion of identity that's distinct from the account itself. If a cluster is configured via OAuth with it's own identity, it's likely operators will want to use that identity regardless of which storage account a job uses.

      So OAuth configs right now (and probably others) are looked up with <config_key>.<account>. I propose that we add a function for looking up these configs that returns an account-specific value if it exists, but in the event it does not will also try to return <config_key>, if that exists.

      I can work on a patch for this if nobody has any objections.

        Attachments

        1. HADOOP-15694.001.patch
          40 kB
          Sean Mackrory
        2. HADOOP-15694.002.patch
          87 kB
          Sean Mackrory
        3. HADOOP-15694.003.patch
          88 kB
          Sean Mackrory
        4. HADOOP-15694-HADOOP-15407.003.patch
          88 kB
          Sean Mackrory
        5. HADOOP-15694-HADOOP-15407.004.patch
          89 kB
          Sean Mackrory
        6. HADOOP-15694-HADOOP-15407.006.patch
          88 kB
          Sean Mackrory
        7. HADOOP-15694-HADOOP-15407.007.patch
          95 kB
          Sean Mackrory
        8. HADOOP-15694-HADOOP-15407.008.patch
          96 kB
          Sean Mackrory
        9. HADOOP-15694-HADOOP-15407-005.patch
          88 kB
          Da Zhou

          Activity

            People

            • Assignee:
              mackrorysd Sean Mackrory
              Reporter:
              mackrorysd Sean Mackrory
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: