Details

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

      Description

      Currently you can configure a nonsensical AWS region for DynamoDB and it doesn't stop you - it'll just start using another region silently. I propose that we just check it's a valid region for the current SDK and throw an exception instead of proceeding.

        Attachments

        1. HADOOP-14181-HADOOP-13345.003.patch
          4 kB
          Sean Mackrory
        2. HADOOP-14181-HADOOP-13345.002.patch
          4 kB
          Sean Mackrory
        3. HADOOP-14181-HADOOP-13345.001.patch
          4 kB
          Sean Mackrory

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: