Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-15619 Über-JIRA: S3Guard Phase IV: Hadoop 3.3 features
  3. HADOOP-16362

ITestS3GuardToolDynamoDB.testDynamoDBInitDestroyCycle fails if test bucket isn't on demand

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 3.3.0
    • Fix Version/s: None
    • Component/s: fs/s3, test
    • Labels:
      None
    • Target Version/s:

      Description

      After HADOOP-15563, if the default s3guard bucket for an FS isn't on-demand, then ITestS3GuardToolDynamoDB.testDynamoDBInitDestroyCycle fails.

      This is because it creates an on-demand DDB table using a dynamodb// ref, but then calls set-capacity on the original FS URL -which then uses any existing table if it is present. And if that table is provisioned, the set capacity call succeeds.

      Fix: the set-capacity call to take the dynamodb:// URL too

        Attachments

          Activity

            People

            • Assignee:
              stevel@apache.org Steve Loughran
              Reporter:
              stevel@apache.org Steve Loughran
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: