pvary commented on issue #13800: URL: https://github.com/apache/iceberg/issues/13800#issuecomment-3204408186
> We could add the cache to HiveCatalog itself; we can probably 'drive' its existence through configuration. (for ref, [apache/hive#6022](https://github.com/apache/hive/pull/6022) is the attempt at fixing the cache in HiveMetastore) How do you handle cases when multiple threads are using the same table instance? Let's say 2 threads are holding a reference to the same table: - T1 fetches TBL from the catalog - T2 fetches TBL from the catalog - T1 reads some of the metadata from TBL - T2 refreshes TBL - T1 reads other part of the metadata from the TBL The 2 metadata reads could be inconsistent, even though T1 did not refresh between the 2 reads. Thanks, Peter -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
