bharatviswa504 commented 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. > > Thanks. I think we need additional s3 tests as the behavior what I tested above (and failing) is not part of the current test suite. > > > Uploaded design doc has provided reasoning to perform on the OM side. > > Thanks to share it. Now I understood the motivation. But what is your opinion about the AWS compatibility? For me it seems to be a bigger problem compared to having the validation code in one at the OM or one place at the client side. > > What is your opinion about AWS compatibility issues? When this flag is enabled, 333 > > 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. > > Thanks. I think we need additional s3 tests as the behavior what I tested above (and failing) is not part of the current test suite. > > > Uploaded design doc has provided reasoning to perform on the OM side. > > Thanks to share it. Now I understood the motivation. But what is your opinion about the AWS compatibility? For me it seems to be a bigger problem compared to having the validation code in one at the OM or one place at the client side. > > What is your opinion about AWS compatibility issues? Currently, the test is simulated in the Integration test. As when this flag is enabled user has chosen to consider key as unix paths. I will add a test suite in HDDS-4154. For now, all tests are in integration tests. ``` <property> <name>ozone.om.enable.filesystem.paths</name> <tag>OZONE, OM</tag> <value>false</value> <description>If true, key names will be interpreted as file system paths. "/" will be treated as a special character and paths will be normalized and must follow Unix filesystem path naming conventions. This flag will be helpful when objects created by S3G need to be accessed using OFS/O3Fs. If false, it will fallback to default behavior of Key/MPU create requests where key paths are not normalized and any intermediate directories will not be created or any file checks happens to check filesystem semantics. </description> </property> ``` So, test/file/ will be normalized to test/file. This PR provides user ability to read with the same file name user has used during the creation of key "test/file/". ---------------------------------------------------------------- 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: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
