xndai commented on PR #17388: URL: https://github.com/apache/iceberg/pull/17388#issuecomment-5112328184
``` If "X" is at a different state when a subsequent load comes in, you essentially get two different "X" tables in the same query plan. This leads to a broken plan that produces very wrong results. So the CachingCatalog exists (partly) to avoid this scenario. ``` I think this is totally a client's responsibility and client's choice. When to refresh "X" completely depends on the transaction semantics provided by the client. Say if client does "Read Committed", then they can refresh any time they want as long as they read the committed snapshots. And if the semantics is "Snapshot Read", then the snapshot "X" needs to remain unchanged for the duration of the transaction. To force a refresh on server side using a TTL seems wrong to me. -- 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]
