FANNG1 commented on PR #10536: URL: https://github.com/apache/gravitino/pull/10536#issuecomment-4126362117
Maybe another option is to push the ETag / conditional-load logic down into the `loadTable` path itself, instead of exposing a separate `getTableMetadataLocation(...)` interface. For example, we could extend `loadTable` to support a conditional request and return either `304` or `LoadTableResponse`. That way: - we do not need to expose a storage/detail-oriented interface just for HTTP caching - the fast path can still reuse the existing `loadTable` event/hook chain - the ETag logic stays encapsulated in one place This feels a bit cleaner to me than adding a separate metadata-location lookup API. -- 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]
