hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elek, Marton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDDS-520) Implement HeadBucket REST endpoint
Date Mon, 01 Oct 2018 12:13:00 GMT

    [ https://issues.apache.org/jira/browse/HDDS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16633913#comment-16633913

Elek, Marton commented on HDDS-520:


It looks good to me after HDDS-560

I tried to test goofys with the current state of our s3g and one problem was that it expected
404 for the missing keys. This patch solves this problem (the other problem was that the list
object also should return with 404 if the prefix doesn't exist)

> Implement HeadBucket REST endpoint
> ----------------------------------
>                 Key: HDDS-520
>                 URL: https://issues.apache.org/jira/browse/HDDS-520
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Elek, Marton
>            Assignee: Bharat Viswanadham
>            Priority: Major
>              Labels: newbie
>         Attachments: HDDS-520.00.patch
> This operation is useful to determine if a bucket exists and you have permission to access
it. The operation returns a 200 OK if the bucket exists and you have permission to access
it. Otherwise, the operation might return responses such as 404 Not Found and 403 Forbidden.
> See the reference here:
> https://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketHEAD.html

This message was sent by Atlassian JIRA

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

View raw message