yuqi1129 commented on issue #12019:
URL: https://github.com/apache/gravitino/issues/12019#issuecomment-5043031775

   Correctness scope that should be treated as prerequisites or acceptance 
criteria for this subtask:
   
   - Reconcile the type allowlist in #12018 with the policy audit in #12149.
   - Depend on the complete, transactional mutation-event coverage tracked by 
#12151; tag/policy emit points alone do not cover non-rename ALTER, 
enable/disable, overwrite/import/repair, rename old/new keys, and other bypass 
paths.
   - Treat #11736 accurately: PR #11739 adds per-listener retry but 
deliberately does not prevent the auto-increment commit-order miss.
   - Verify the remaining late-fill race after #10740: a load may start before 
post-commit invalidation and write its old result after invalidation. Cover 
both `get` and `batchGet`, plus hierarchical drops.
   - Drain backlogs larger than one batch and expose lag/listener health; do 
not promise convergence within one poll interval unless the implementation and 
tests establish that bound.
   - Use a bounded `expireAfterWrite` safety backstop rather than relying on 
`expireAfterAccess` for hot keys.
   
   The precise Caffeine contract should be bounded eventual consistency. 
Operations that cannot accept that window are tracked by the fresh-read work in 
#12150.
   


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