[
https://issues.apache.org/jira/browse/HADOOP-15635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588954#comment-16588954
]
Sean Mackrory commented on HADOOP-15635:
----------------------------------------
{quote}once you have the FS, you can use S3AFileSystem.hasMetadataStore(){quote}
Well we made it pretty flexible to specify what metadatastore you're talking
about (and maybe that was a mistake), and you don't even have to specify enough
context to get an FS instance. For instance, I'm pretty sure you can purge all
old metadata from a DynamoDB table by specifying "-m
dynamo://my_table_to_parge" and that might pertain to metadata for multiple
buckets, so there's no way to create an FS instance from that.
So I thinking checking that the configured implementation doesn't end up being
null (after per-bucket configs are taken into account) is the right thing to
do, but we also need to make sure that the user didn't actually provide a
specific implementation and table name in the form of the -m URL. Does that
make sense?
> s3guard set-capacity command to fail fast if bucket is unguarded
> ----------------------------------------------------------------
>
> Key: HADOOP-15635
> URL: https://issues.apache.org/jira/browse/HADOOP-15635
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.2.0
> Reporter: Steve Loughran
> Assignee: Gabor Bota
> Priority: Minor
> Attachments: HADOOP-15635.001.patch
>
>
> If you try to do {{hadoop s3guard set-capacity s3a://landsat-pds}}, or any
> other bucket which exists but doesn't have s3guard enabled, you get a stack
> trace reporting that the ddb table doesn't exist.
> the command should check for the bucket being guarded and fail on that
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
