[
https://issues.apache.org/jira/browse/HADOOP-13449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mingliang Liu updated HADOOP-13449:
-----------------------------------
Attachment: HADOOP-13449-HADOOP-13345.002.patch
Thanks all for the insightful comments! I changed the patch accordingly, with
some comments to address in the next patch (I'm actively working on v3 patch
now):
# We assume the client/callers have pre-create all the parents of the path.
This is different from in-memory local store. Put itself will not check this
and will not fail. As we should fail if the parent directories are missing, we
fail later (e.g. in S3A#close).
# Sorry the "isAuthorative" is not stored yet. I'm confused when to set/get the
value. Is this purely controlled by the client?
# Bumping the AWS SDK version is a prerequisite. This patch bumps for test
purpose.
# Will make the "DDBMetadataStore" 1:1 mapping with the table. So
{{createTable}}, {{deleteTable}} and {{provisionTable}} will all take no table
names.
# Will add more logic to guard the {{isEmpty}} field.
> S3Guard: Implement DynamoDBMetadataStore.
> -----------------------------------------
>
> Key: HADOOP-13449
> URL: https://issues.apache.org/jira/browse/HADOOP-13449
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Chris Nauroth
> Assignee: Mingliang Liu
> Attachments: HADOOP-13449-HADOOP-13345.000.patch,
> HADOOP-13449-HADOOP-13345.001.patch, HADOOP-13449-HADOOP-13345.002.patch
>
>
> Provide an implementation of the metadata store backed by DynamoDB.
--
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
