dpol1 opened a new pull request, #3011:
URL: https://github.com/apache/hugegraph/pull/3011

   ## Purpose of the PR
   
   - close #2617
   
   In HStore / multi-server mode, schema changes can leave other server nodes 
with stale local schema caches. `CachedSchemaTransactionV2` already publishes 
schema-cache clear events through `MetaManager`, but it did not listen for 
those meta events and clear the affected local V2 caches.
   
   ## Main Changes
   
   - Register a JVM-wide schema cache clear listener for 
`CachedSchemaTransactionV2`
   - Clear V2 `schema-id` / `schema-name` caches and the attached array cache 
by graph name
   - Publish schema cache clear events after schema add, update, and remove 
paths
   - Keep the local `EventHub` cache listener registered per transaction 
instance
   - Add unit coverage for graph-scoped V2 schema cache clearing
   
   ## Verifying these changes
   
   - [ ] Trivial rework / code cleanup without any test coverage. (No Need)
   - [ ] Already covered by existing tests, such as *(please modify tests 
here)*.
   - [x] Need tests and can be verified as follows:
       - `mvn test -pl hugegraph-server/hugegraph-test -am -P unit-test 
-Dtest=CachedSchemaTransactionTest -DfailIfNoTests=false "-Djacoco.skip=true"`
   
   ## Does this PR potentially affect the following parts?
   
   - [ ]  Dependencies ([add/update 
license](https://hugegraph.apache.org/docs/contribution-guidelines/contribute/#321-check-licenses)
 info & 
[regenerate_known_dependencies.sh](../install-dist/scripts/dependency/regenerate_known_dependencies.sh))
   - [ ]  Modify configurations
   - [ ]  The public API
   - [x]  Other affects: HStore schema cache invalidation behavior in 
multi-server deployments
   - [ ]  Nope
   
   ## Documentation Status
   
   - [ ]  `Doc - TODO`
   - [ ]  `Doc - Done`
   - [x]  `Doc - No Need`
   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to