Caideyipi opened a new pull request, #18888:
URL: https://github.com/apache/iotdb/pull/18888

   ## Description
   
   The deletion regression tests set `managedByFlushManager` before calling 
`asyncClose()`, so its guard returns before queuing the working memtable. This 
breaks both deletion WAL tests and causes a null-future exception during 
cleanup of the flush-completion test.
   
   Claim manual flush control in the flush-time callback, after the close guard 
and before FlushManager registration. This lets the tests exercise the 
production close path while retaining control over flush execution and checking 
deletion persistence.
   
   ## Validation
   
   - Previous validation of this fix: `TsFileProcessorTest` — 26 tests passed.
   - `mvn spotless:apply -pl iotdb-core/datanode` — passed.
   - `git diff --check origin/master...HEAD` — passed.
   
   <hr>
   
   This PR has:
   
   - [x] been self-reviewed.
   - [x] added comments explaining the intent of the flush-control callback.
   - [x] modified existing unit tests to exercise the close path and verify 
deletion WAL records and persisted modifications.
   
   <hr>
   
   ##### Key changed classes
   
   - `TsFileProcessorTest`
   


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