imbajin commented on PR #3159:
URL: https://github.com/apache/hugegraph/pull/3159#issuecomment-5457674257
TODO follow-ups intentionally kept out of this minimal API 0.72 closeout:
1. Design an explicit, versioned migration/cleanup path for legacy
`<graph>_observer` bindings, including deleted-and-recreated graph names.
API 0.72 now uses explicit `ALL_GRAPHS`; request-time graph scans and
hidden
role mutation were removed rather than extended.
Context:
https://github.com/apache/hugegraph/pull/3159#discussion_r3838617173
2. Coordinate graph deletion with concurrent data/schema mutations through
one
documented graph-wide lifecycle gate, including lock ordering and a
concurrency regression. This spans the existing `storeProvider.clear()`
boundary and should not be approximated by a local HStore-only lock.
Context:
https://github.com/apache/hugegraph/pull/3159#discussion_r3838617174
3. Define exact-once schema-cache notification ownership for HStore graph
clear
without losing the direct broadcast required when
`task.sync_deletion=true`. The final code preserves correctness and may
emit
a bounded duplicate under the default asynchronous-deletion path.
Context:
https://github.com/apache/hugegraph/pull/3159#discussion_r3838617176
These are explicit follow-ups, not silently implemented compatibility
behavior
in this PR. The final head keeps the HStore metadata/cache clear bugfix,
restores
the required direct remote invalidation, and leaves broader lifecycle/event
redesign for a separately scoped change.
--
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]
