[ https://issues.apache.org/jira/browse/HDDS-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16644957#comment-16644957 ]
Elek, Marton commented on HDDS-517: ----------------------------------- +1. Thank you very much the update [~GeLiXin] I tested it and worked well. (After HDDS-523 – which includes significant modification in awscli.robot – we can add additional robot tests for this). Will commit it soon. ps: Sorry for the confusion for the Content-Length. You were right. It should be the length of the file as it works now. It was my fault, I tested it with a wrong file. ps2: I removed the unused imports during the commit. > Implement HeadObject REST endpoint > ---------------------------------- > > Key: HDDS-517 > URL: https://issues.apache.org/jira/browse/HDDS-517 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task > Reporter: Elek, Marton > Assignee: LiXin Ge > Priority: Major > Labels: newbie > Attachments: HDDS-517.000.patch, HDDS-517.001.patch, > HDDS-517.002.patch > > > The HEAD operation retrieves metadata from an object without returning the > object itself. This operation is useful if you are interested only in an > object's metadata. To use HEAD, you must have READ access to the object. > Steps: > 1. Look up the volume > 2. Read the key and return to the user. > The AWS reference is here: > https://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectHEAD.html > We have a simple version of this call in HDDS-444 but without Range support. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org