You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by GitBox <gi...@apache.org> on 2020/08/26 21:08:58 UTC
[GitHub] [hadoop-ozone] bharatviswa504 edited a comment on pull request #1328: HDDS-4102. Normalize Keypath for lookupKey.
bharatviswa504 edited a comment on pull request #1328:
URL: https://github.com/apache/hadoop-ozone/pull/1328#issuecomment-681124935
> Tested and `file/` and `file` are different:
>
> ```
> $ aws s3api get-object --bucket=ozonetest --key=test1/file /tmp/www
> {
> "AcceptRanges": "bytes",
> "LastModified": "Wed, 26 Aug 2020 14:24:06 GMT",
> "ContentLength": 79,
> "ETag": "\"6fcb0dbe8f0ef330b38f81a6a6a7a66e\"",
> "ContentType": "text/markdown",
> "Metadata": {}
> }
> ```
>
> ```
> aws s3api get-object --bucket=ozonetest --key=test1/file/ /tmp/www
>
> An error occurred (NoSuchKey) when calling the GetObject operation: The specified key does not exist.
> ```
>
> Just an idea: what do you think about normalizing the path on the client side? (o3fs/ofs). Would it make any problems?
Thank You @elek for the test.
Uploaded design doc has provided reasoning to perform on the OM side.
And also when used via ofs/o3fs, it uses path Object, and paths are normalized already.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org