LiJie20190102 opened a new issue, #13429:
URL: https://github.com/apache/gravitino/issues/13429
### Describe the subtask
Write the design document for the reconcile mechanism in the parent epic:
what "stale" means per entity type, how to confirm absence in the source
(explicit per-object existence probe, never a listing; distinguish
source-unreachable from absent), the trigger options (periodic server-side
task and/or on-demand API), and the policy (report-only vs
report-and-remove).
The design must cover removal through the dispatcher chain under the server's
tree lock, so events, secret cleanup, authorization-plugin privilege removal
and orphan cleanup behave exactly as an explicit drop.
Acceptance:
- Design document merged under `design-docs/`.
- Open questions (rename handling via `gravitino.identifier`, system
identity for the background task, per-catalog policy, removal rate
limiting) recorded for community discussion.
### Parent issue
#13313
--
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]
