[GitHub] [iceberg] mechgouki removed a comment on pull request #2847: [2806]Dell EMC ECS features required by a new ECS Catalog impl

[GitBox <gi...@apache.org>]

mechgouki removed a comment on pull request #2847:
URL: https://github.com/apache/iceberg/pull/2847#issuecomment-916530749


   > @wang-x-xia, the 3-clause BSD license is compatible with the Apache License: https://www.apache.org/legal/resolved.html
   > 
   > It is listed as Category A. So it should be fine.
   > 
   > What is the rationale for using a library specific to EMC rather than the S3 v1 API? It seems like the S3 v1 API is probably going to be useful to more people. Are there EMC features that we can only get using the EMC client? You mentioned append support, but all of the formats that Iceberg uses are immutable. So we never need to re-open a file and append more data.
   
   
   Basically we have 2 areas which Dell EMC features could benefit :
   (1)Append operation in additional of MPU, if the client has less local cache for large object( like edge), Dell EMC object service could help here.
   (2)Atomic rename.  We have If-Match and If-None-Match semantic as we support strong consistency model (within one site) from the very beginning.
   
   And talked internally, for better support the customer, if we use Dell EMC  features, we'd better use our own client with BSD License.  AWS S3 V1 could be workaround here, but V2 can not be a option .
   
   Looking forward for your suggestion here
   


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

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org