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

Client should always ask namenode for kms provider path.

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.9.0, 3.0.0-alpha4, 2.8.2
    • kms
    • None

    Description

      According to current implementation of kms provider in client conf, there can only be one kms.
      In multi-cluster environment, if a client is reading encrypted data from multiple clusters it will only get kms token for local cluster.
      Not sure whether the target version is correct or not.

      Attachments

        1. HADOOP-14104-branch-2.8.patch
          38 kB
          Rushabh Shah
        2. HADOOP-14104-branch-2.patch
          38 kB
          Rushabh Shah
        3. HADOOP-14104-trunk.patch
          28 kB
          Rushabh Shah
        4. HADOOP-14104-trunk-v1.patch
          30 kB
          Rushabh Shah
        5. HADOOP-14104-trunk-v2.patch
          39 kB
          Rushabh Shah
        6. HADOOP-14104-trunk-v3.patch
          38 kB
          Rushabh Shah
        7. HADOOP-14104-trunk-v4.patch
          38 kB
          Rushabh Shah
        8. HADOOP-14104-trunk-v5.patch
          38 kB
          Rushabh Shah

        Issue Links

          Activity

            People

              shahrs87 Rushabh Shah
              shahrs87 Rushabh Shah
              Votes:
              0 Vote for this issue
              Watchers:
              18 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: