snazy commented on PR #433: URL: https://github.com/apache/polaris/pull/433#issuecomment-2497924249
Actually, I think loading/saving table metadata should be transparently done, using a delegating code architecture. Think: a (REST) resource asks for metadata "abc" using some interface `IcebergMetadataStore` (or so). There would be multiple implementations of that interface: * one that interacts with the actual object store * one that is implemented as a delegate to the one that interacts with the object store, but also provides a caching mechanism That way the calling code does not need to care about caching at all, and testing would be quite isolated. Using such an interface with various implementations/delegates can also ease testing quite a bit. -- 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]
