hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bharat Viswanadham (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (HDDS-742) Handle object list requests (GET bucket) without prefix parameter
Date Tue, 30 Oct 2018 03:04:00 GMT

     [ https://issues.apache.org/jira/browse/HDDS-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bharat Viswanadham updated HDDS-742:
------------------------------------
    Comment: was deleted

(was: Handled this issue also in HDDS-659 (as to make continuation-token work we need complete
changes), but HDDS-659 should be applied on top of this change. 

 )

> Handle object list requests (GET bucket) without prefix parameter
> -----------------------------------------------------------------
>
>                 Key: HDDS-742
>                 URL: https://issues.apache.org/jira/browse/HDDS-742
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>          Components: S3
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
>         Attachments: HDDS-742.001.patch, HDDS-742.02.patch
>
>
> In s3 gateway the GET bucket endpoint is already implemented. It can return with the
available objects based on a given prefix.
> ([https://docs.aws.amazon.com/AmazonS3/latest/API/v2-RESTBucketGET.html)]
> As it's defined the Delimiter parameter is used to reduce the response with returning
only the first-level keys and prefixes (aka directories)
> {code:java}
> <ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
>   <Name>example-bucket</Name>
>   <Prefix></Prefix>
>   <KeyCount>2</KeyCount>
>   <MaxKeys>1000</MaxKeys>
>   <Delimiter>/</Delimiter>
>   <IsTruncated>false</IsTruncated>
>   <Contents>
>     <Key>sample.jpg</Key>
>     <LastModified>2011-02-26T01:56:20.000Z</LastModified>
>     <ETag>&quot;bf1d737a4d46a19f3bced6905cc8b902&quot;</ETag>
>     <Size>142863</Size>
>     <StorageClass>STANDARD</StorageClass>
>   </Contents>
>   <CommonPrefixes>
>     <Prefix>photos/</Prefix>
>   </CommonPrefixes>
> </ListBucketResult>{code}
> Here we can have multiple additional objects with photos/ prefix but they are not added
to the response.
>  
> The main problem in the ozone s3 implementation is that the Delimiter parameter *should
be optional.* In case of the delimiter is missing we should always return all the keys without
any common prefix simplification.
> It requires for recursive directory listing which is used by s3a adapter.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message