[ https://issues.apache.org/jira/browse/HADOOP-13876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mingliang Liu reassigned HADOOP-13876: -------------------------------------- Assignee: Mingliang Liu > S3Guard: better support for multi-bucket access including read-only > ------------------------------------------------------------------- > > Key: HADOOP-13876 > URL: https://issues.apache.org/jira/browse/HADOOP-13876 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 > Affects Versions: HADOOP-13345 > Reporter: Aaron Fabbri > Assignee: Mingliang Liu > Attachments: HADOOP-13876-HADOOP-13345.000.patch > > > HADOOP-13449 adds support for DynamoDBMetadataStore. > The code currently supports two options for choosing DynamoDB table names: > 1. Use name of each s3 bucket and auto-create a DynamoDB table for each. > 2. Configure a table name in the {{fs.s3a.s3guard.ddb.table}} parameter. > One of the issues is with accessing read-only buckets. If a user accesses a > read-only bucket with credentials that do not have DynamoDB write > permissions, they will get errors when trying to access the read-only bucket. > This manifests causes test failures for {{ITestS3AAWSCredentialsProvider}}. > Goals for this JIRA: > - Fix {{ITestS3AAWSCredentialsProvider}} in a way that makes sense for the > real use-case. > - Allow for a "one DynamoDB table per cluster" configuration with a way to > chose which credentials are used for DynamoDB. > - Document limitations etc. in the s3guard.md site doc. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org