[
https://issues.apache.org/jira/browse/HDDS-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16657269#comment-16657269
]
Bharat Viswanadham edited comment on HDDS-658 at 10/19/18 6:48 PM:
-------------------------------------------------------------------
[~elek]
For this jira, you are proposing to have an implementation in OM which takes
the username, and returns the Volume for that user if it exists or else return
"NO VOLUME for User" (where can check this to just return empty response). Let
me know if my understanding is correct.
was (Author: bharatviswa):
[~elek]
For this jira, you are proposing to have an implementation in OM which takes
the username, and returns the Volume for that user if it exists or else return
"NO VOLUME for User" (where can map this to just return empty response). Let me
know if my understanding is correct.
> 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
>
> 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]
