[
https://issues.apache.org/jira/browse/HADOOP-13449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716725#comment-15716725
]
Mingliang Liu commented on HADOOP-13449:
----------------------------------------
Thanks [~fabbri]. Quick reply (I'm working on this as well, will keep posted):
# For point 1, let's track elsewhere.
# For point 2, the explanation makes sense. My current in-progress change is to
remove the "isEmpty" field from DynamoDB (DDB) table for directories, and to
issue a query DDB request whose "parent" field is the current directory. Then I
realized that, there may be items in the table whose ancestor (parent of
parent, say) is the given directory, but their parent directories are missing.
e.g for {{/a, /a/b/c, /a/b/d}}, {{/a}} is not empty. This has some similar
problem to point 3. A simply query seems not enough.
# For point 3, yes we may have to use scan as the hash key is not known. Let's
figure out the best solution.
> 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,
> HADOOP-13449-HADOOP-13345.003.patch, HADOOP-13449-HADOOP-13345.004.patch,
> HADOOP-13449-HADOOP-13345.005.patch, HADOOP-13449-HADOOP-13345.006.patch,
> HADOOP-13449-HADOOP-13345.007.patch, HADOOP-13449-HADOOP-13345.008.patch,
> HADOOP-13449-HADOOP-13345.009.patch, HADOOP-13449-HADOOP-13345.010.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: [email protected]
For additional commands, e-mail: [email protected]
