ealeonraz commented on issue #12150: URL: https://github.com/apache/gravitino/issues/12150#issuecomment-5154491688
I'd like to work on this one. It is the fresh-read contract I referenced in #12020, so I have already been reasoning about the boundary between cached reads and consistency-sensitive ones. Plan: add an explicit fresh-read mode to `get`/`batchGet` that bypasses both cache lookup and refill unless the refill is version-fenced, then audit the consistency-sensitive call sites listed here (metalake usage-state preconditions, policy state transitions, job status and cancellation, job template execution, fileset paths and credentials used for external I/O, catalog provider properties, and managed schema/table reads used as write preconditions), leaving ordinary metadata reads on the cached path. I'll add metrics for fresh reads and tests that inject a stale cache entry and assert sensitive operations still observe current state. Please assign it to me if it's available. -- 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]
