[
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.000.patch
{quote}
When do table.query() in listChildren(), the query might return partial results
because the returned dataset is large. You can use {{
QueryResult#LastEvaluatedKey()}} for the following calls.
{quote}
The {{table.query()}} is using the document model, whose response includes an
ItemCollection object that provides all items returned by the query. This is
simpler and clearer than old {{AmazonDynamoDBClient#query()}}. See
http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/QueryingJavaDocumentAPI.html
{quote}
We should store more metadata beside is_directory in metadata.
{quote}
Agreed. There are 3 unit tests failing because of this. I'm wondering whether
we should also save access time, owner, group, permission, size etc in the
metadata, as {{verifyBasicFileStatus}} and {{verifyDirStatus}} test a few.
Other comments are addressed in the v0 patch.
I still need to pass the 4/15 failing unit tests before the patch is in a good
shape. Meanwhile, I'll review related patches and rebase the patch for
{{FileStatus}}. The {{DirListingMetadata#isAuthoritative}} flag is not yet
taken care of when putting/listing children. I'll post a refined v1 patch to
address the above concerns this week.
Thanks,
> 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
>
>
> 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]
