yuqi1129 opened a new pull request, #10416:
URL: https://github.com/apache/gravitino/pull/10416

   ### What changes were made?
   
   This PR implements Phase-1 cache invalidation unification for #10414.
   
   - Added a shared cache invalidation framework under core:
     - CacheDomain, CacheInvalidationEvent, CacheInvalidationOperation
     - CacheInvalidationHandler, CacheInvalidationService
     - local in-JVM dispatcher implementation and factory
     - typed invalidation keys for entity/catalog/role/owner caches
   - Added config toggle:
     - gravitino.cache.invalidation.enabled (default: true)
   - Wired unified invalidation into:
     - RelationalEntityStore (entity/relation mutations including batchPut and 
batchDelete)
     - CatalogManager (catalog cache invalidation paths)
     - JcasbinAuthorizer (loadedRoles and ownerRel invalidation)
   - Added tests:
     - TestLocalCacheInvalidationService
   
   ### Why are the changes needed?
   
   Cache invalidation logic was previously spread across modules with 
inconsistent mutation coverage. This change introduces a shared contract and 
local dispatcher so invalidation behavior is explicit and consistent across key 
high-risk modules.
   
   ### Does this PR introduce any user-facing change?
   
   No functional API change. Internal cache invalidation behavior is 
standardized.
   
   ### How was this patch tested?
   
   - ./gradlew :core:spotlessApply :server-common:spotlessApply --no-daemon
   - ./gradlew :core:compileJava :server-common:compileJava :core:test --tests 
org.apache.gravitino.cache.invalidation.TestLocalCacheInvalidationService 
:core:test --tests org.apache.gravitino.catalog.TestCatalogManager 
:server-common:test --tests 
org.apache.gravitino.server.authorization.jcasbin.TestJcasbinAuthorizer 
--no-daemon
   
   Closes #10414
   


-- 
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]

Reply via email to