ealeonraz commented on issue #12020: URL: https://github.com/apache/gravitino/issues/12020#issuecomment-5647674589
Yes, still on it. The PR is up: https://github.com/apache/gravitino/pull/13106. It implements the design above, scoped as a shared cache: single-slot Lua scripts keyed by the metalake hash tag, an atomic container drop over the index range, and a fence check on every fill so a load that began before a drop cannot refill the key. Reads and fills degrade to a miss on a Redis failure; a failed invalidation is propagated rather than swallowed. On the three questions from my last comment I went with metalake-level hash tags, Jedis plus Kryo, and a single PR with both the standalone and cluster integration tests included. Happy to split the tests out if the review is easier that way. -- 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]
