Caideyipi commented on PR #19171:
URL: https://github.com/apache/iotdb/pull/19171#issuecomment-6683613532

   Initial self-review summary
   
   - Finding: An older LAST query may still update the last-value cache after a 
same-name schema is dropped and recreated. Available logs do not establish that 
this race caused the reported symptom. A complete generation guard crosses 
planning, distributed plan transport, cache concurrency, and 
multi-node/multi-Region tests, so it is deferred as documented in the PR.
   - Fix: Tree last-cache initialization, update, and invalidation no longer 
repopulate schema cache; protected schema acquisition and creation paths remain 
responsible for schema population.
   - Verification: Spotless and `git diff --check` passed. Local clean DataNode 
reactor tests passed: 20 tests, 0 failures, 0 errors, with main and test 
sources compiled. Full server integration tests, master runtime validation, and 
field validation were not run.
   - Reviewed SHA: `3002d3f6acca7eee6b8ea9ca9f2e158d65b93874`.
   - Final local SHA: `3002d3f6acca7eee6b8ea9ca9f2e158d65b93874`.
   - Confirmed remote branch and PR head SHA: 
`3002d3f6acca7eee6b8ea9ca9f2e158d65b93874`.
   - Incomplete: Remote CI was not awaited; full server integration tests, 
master runtime validation, and field validation remain unrun.
   


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