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/09/14 22:44:46 UTC

[GitHub] [hadoop-ozone] avijayanhwx commented on pull request #1418: HDDS-4209. S3A Filesystem does not work with Ozone S3.

avijayanhwx commented on pull request #1418:
URL: https://github.com/apache/hadoop-ozone/pull/1418#issuecomment-692353079


   > 1. bject-store endpoints.
   
   Thanks for working on this @bharatviswa504  and reviewing it @elek.
   
   My 2 cents.
   
   Overall, I am OK with this approach.
   
   In my mind, the s3g is a component whose principal responsibility is to support s3 use cases on Ozone as much as possible (hopefully 100%). The s3g belongs to Ozone world, and would be the right place to make changes for anything that needs knowledge of Ozone API internals for supporting s3 related APIs.
    
   If we retain the trailing "/" for files that are of "0" byte, we would need to think about how to support the use case of creating a zero byte file, and appending to it. 
   
   I don't think we should add more configs to solve this problem. I would rather have 95% support of s3 in the short term than add more complexity and "states" OM APIs can be in based on config values.


----------------------------------------------------------------
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