lsyulong commented on issue #7663: URL: https://github.com/apache/gravitino/issues/7663#issuecomment-3101485124
Thank you @lizc9 for raising the locking mechanism question! This is indeed a key consideration for the Paimon REST Server implementation. I see that Gravitino already has a TreeLock mechanism, so we can implement based on this rather than relying on the underlying Hive Catalog locks. Here are the reasons: Architectural Consistency Gravitino already has a complete hierarchical locking system - TreeLock. Existing Implementation Reference TreeLock is already widely used in Gravitino's core Dispatcher layer. Existing Iceberg REST Server Locking Mechanism Reference The Iceberg REST Server itself doesn't directly implement locks - it indirectly benefits from TreeLock protection by calling Gravitino's core Dispatcher layer. So, can the Paimon REST Server leverage previous experience during implementation? What do you think of this approach? Welcome further discussion! -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
