[
https://issues.apache.org/jira/browse/HADOOP-13448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15491681#comment-15491681
]
Aaron Fabbri commented on HADOOP-13448:
---------------------------------------
Just saw your followup comment.
How about this idea: We keep MetadataStore independent of particular
implementations' dependencies, but add extra parameters as needed for
implementations.
e.g. MetadataStore could eventually be separate submodule in Hadoop Common,
with DynamoDBMetadataStore living in hadoop-aws and taking additional init
parameters for S3 client, etc.
Then, for example, Swift/WASB/ADLS could also have implementations that require
additional dependencies (e.g. AzureDBMetadataStore).
Another way of thinking of this is, MetadataStore interface only includes
things that all implementations have in common, instead of providing a union of
everything all the implementations use.
> S3Guard: Define MetadataStore interface.
> ----------------------------------------
>
> Key: HADOOP-13448
> URL: https://issues.apache.org/jira/browse/HADOOP-13448
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Fix For: HADOOP-13345
>
> Attachments: HADOOP-13448-HADOOP-13345.001.patch,
> HADOOP-13448-HADOOP-13345.002.patch, HADOOP-13448-HADOOP-13345.003.patch,
> HADOOP-13448-HADOOP-13345.004.patch, HADOOP-13448-HADOOP-13345.005.patch
>
>
> Define the common interface for metadata store operations. This is the
> interface that any metadata back-end must implement in order to integrate
> with S3Guard.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
