[
https://issues.apache.org/jira/browse/HDDS-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16688528#comment-16688528
]
Bharat Viswanadham commented on HDDS-658:
-----------------------------------------
Hi [~elek]
{quote}The code calculates the s3 volume name based on specific user name and
lists all the ozone buckets inside them. It's possible that some evil user
(=me) creates ozone-only buckets in a s3 volume. In this case the list will be
bad (fix me If I am wrong) as it includes both the s3 and ozone-only buckets.
{quote}
Does ozone bucket means, buckets created through ozone shell? If so, then you
are proposing that when we list buckets for a user, we should not show the
buckets created through ozone shell, This makes sense, as these buckets are not
of that user. I think for this, we can have a type in the bucketInfo, and
during listing, we can avoid showing this.
So, I have a question then when we list all buckets in the volume through ozone
shell, do we want to list only the ozone buckets or all buckets.
> Implement s3 bucket list backend call and use it from rest endpoint
> -------------------------------------------------------------------
>
> Key: HDDS-658
> URL: https://issues.apache.org/jira/browse/HDDS-658
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Components: S3
> Reporter: Elek, Marton
> Assignee: Bharat Viswanadham
> Priority: Major
> Attachments: HDDS-658.00.patch
>
>
> HDDS-657 provides a very basic functionality for list buckets. There are two
> problems there:
> # It repeats the username -> volume name mapping convention.
> # Doesn't work if volume doesn't exist (no s3 buckets created, yet).
> The proper solution is to do the same on server side:
> # Use the existing naming convention in OM
> # Return empty list in case of value is missing.
> It requires an additional rpc call to the om.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
