bharatviswa504 edited a comment on pull request #1328:
URL: https://github.com/apache/hadoop-ozone/pull/1328#issuecomment-684950217
@elek
There is no issue with this, and I believe we have agreed on the part we
need this like 100% HCFS with few changes to AWS S3 semantics. I don't see
bharatviswa504 edited a comment on pull request #1328:
URL: https://github.com/apache/hadoop-ozone/pull/1328#issuecomment-684950217
@elek
There is no issue with this, and I believe we have agreed on the part we
need this like 100% HCFS with few changes to AWS S3 semantics. I don't see
bharatviswa504 edited a comment on pull request #1328:
URL: https://github.com/apache/hadoop-ozone/pull/1328#issuecomment-684950217
@elek
There is no issue with this. As the other argument is when the flag is
disabled to support HCFS.
And I believe we have agreed on the part we
bharatviswa504 edited a comment on pull request #1328:
URL: https://github.com/apache/hadoop-ozone/pull/1328#issuecomment-682070057
> > Opened a jira
[HDDS-4154](https://issues.apache.org/jira/browse/HDDS-4154) to test S3 test
suite with ozone.om.enable.filesystem.paths enabled.
>
bharatviswa504 edited a comment on pull request #1328:
URL: https://github.com/apache/hadoop-ozone/pull/1328#issuecomment-681125960
> Thanks for the patch @bharatviswa504, I would suggest adding a related
robot test, too, which would make it possible to test the AWS compatibility of
the
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
> {
>
