BsoBird commented on PR #10688:
URL: https://github.com/apache/iceberg/pull/10688#issuecomment-2226738178

   @danielcweeks @rdblue 
   I know what you mean, Sir.
   
   1.About abandoning the catalog implementation that relies on lockManager. I 
think this is too radical. I agree that it would be better to prioritise moving 
towards catalogues that do not rely on lockManager, but it would be better to 
balance this with the use of lockManager (which in itself is not a difficult 
task).For example, a large number of users still use GlueCatalog, because they 
want to access both iceberg and non-iceberg tables in Glue.If we migrate the 
iceberg catalogues to a different store such as database, users will not be 
able to view the iceberg tables in glue, and they may not be able to accept 
this.Because, if they have a choice, they should store the iceberg-catalog in a 
system that doesn't rely on lockManager in the first place.
   
   2.You might think that users could solve this problem by implementing 
rest-catalog. However, many users do not have the ability to implement 
rest-catalog.Also, rest-catalog is still evolving, and many of the 
specifications have not yet been finalised.
   
   3.Regarding the fact that all clients need to be involved in the locking in 
order for it to work. I think this is a problem that users need to solve 
themselves. ICEBERG is just a toolbox and it is up to the user to use it well.
   
   4.Regarding the new lockManager, I also think that we should not continue to 
add more third-party dependencies to the core, so adding redisson is just an 
experiment.If someone refuses, I'll remove it immediately. Only the 
httpLockManager remains. This way, we don't add any additional dependencies to 
iceberg-core.


-- 
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-unsubscr...@iceberg.apache.org

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


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

Reply via email to