[
https://issues.apache.org/jira/browse/HADOOP-13650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei (Eddy) Xu updated HADOOP-13650:
-----------------------------------
Attachment: HADOOP-13650-HADOOP-13345.000.patch
Uploaded a working-in-progress patch. The patch requires that the
{{MetadataStore}} interface and {{DynamoDB}} metadata store to be ready.
[~liuml07], One question I have in the implementation is that, for
{{initialize()}} / {{destroy}} functions, can we provide a version of such
functions that do not take {{S3FIleSystem}} as parameters (i.e., taking
{{Configuration}} instead)? Providing s3a path in {{s3a s3guard init -m <URI>
s3a://bucket/path}} seems be not necessary.
[[email protected]] I've added a new {{s3a}} command in this patch.
Additionally, I proposed to use {{URI}} as metadata store table name, so that
we can support {{dynamodb://}}, {{mysql://}}, {{local://}} and etc.
> S3Guard: Provide command line tools to manipulate metadata store.
> -----------------------------------------------------------------
>
> Key: HADOOP-13650
> URL: https://issues.apache.org/jira/browse/HADOOP-13650
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Lei (Eddy) Xu
> Assignee: Lei (Eddy) Xu
> Attachments: HADOOP-13650-HADOOP-13345.000.patch
>
>
> Similar systems like EMRFS has the CLI tools to manipulate the metadata
> store, i.e., create or delete metadata store, or {{import}}, {{sync}} the
> file metadata between metadata store and S3.
> http://docs.aws.amazon.com//ElasticMapReduce/latest/ReleaseGuide/emrfs-cli-reference.html
> S3Guard should offer similar functionality.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
