You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Bharat Viswanadham (Jira)" <ji...@apache.org> on 2020/07/28 18:55:00 UTC
[jira] [Updated] (HDDS-4044) Deprecate ozone.s3g.volume.name
[ https://issues.apache.org/jira/browse/HDDS-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bharat Viswanadham updated HDDS-4044:
-------------------------------------
Priority: Blocker (was: Major)
> Deprecate ozone.s3g.volume.name
> -------------------------------
>
> Key: HDDS-4044
> URL: https://issues.apache.org/jira/browse/HDDS-4044
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Bharat Viswanadham
> Priority: Blocker
>
> HDDS-3612 introduced bucket links.
> After this feature now we don't need this parameter, any volume/bucket can be exposed to S3 via using bucket links.
> ozone bucket link srcvol/srcbucket destvol/destbucket
> So now to expose any ozone bucket to S3G
> For example, the user wants to expose a bucket named bucket1 under volume1 to S3G, they can run below command
> {code:java}
> ozone bucket link volume1/bucket1 s3v/bucket2
> {code}
> Now, the user can access all the keys in volume/bucket1 using s3v/bucket2 and also ingest data to the volume/bucket1.
> This Jira is opened to remove the config from ozone-default.xml
> And also log a warning message to use bucket links, when it is not default value s3v.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org