hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13449) S3Guard: Implement DynamoDBMetadataStore.
Date Sun, 30 Oct 2016 21:55:58 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-13449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15620639#comment-15620639

Chris Nauroth commented on HADOOP-13449:

bq. Also: that dynamo DB dependency MUST be at {{<provided>}} scope. We don't want to
force it on people.

[~stevel@apache.org], the DynamoDB client adds no transitive dependencies that hadoop-aws
is not already picking up through the AWS SDK.  Here we can see the only dependencies are
on aws-java-sdk-s3 and aws-java-sdk-core:


Everything else is a test-only dependency.

In this case, I wonder if the right trade-off is for us to allow the dependency, so that downstream
projects can pick up S3Guard functionality without needing to add the aws-java-sdk-dynamodb
dependency explicitly.  Those projects would likely need to keep synchronized with whatever
AWS SDK version number we're using in Hadoop, so as to avoid internal version conflicts around
things like aws-java-sdk-core.

> 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
> Provide an implementation of the metadata store backed by DynamoDB.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message