VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • HADOOP-13345
    • fs/s3
    • 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.001.patch
          4 kB
          Sean Mackrory
        2. HADOOP-14181-HADOOP-13345.002.patch
          4 kB
          Sean Mackrory
        3. HADOOP-14181-HADOOP-13345.003.patch
          4 kB
          Sean Mackrory

        Activity

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

          People

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

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment