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

   Backport #19136 (`c6e229aef50608cb67bfb4fd94717d05f4ef3d0f`) to `dev/1.3`, 
based on `cb70919de5e82f184ae60df49172889f7966c2c2`.
   
   The 1.3 local whole-file LOAD path also exposes the final `.tsfile` name 
before its resource and deletions are installed. A DataNode process crash in 
that window can let recovery make deleted values visible again.
   
   Stage the data under `.tsfile.load-pending`, install the resource and 
`.mods`, and publish with a same-directory atomic rename. Keep the complete 
source group until publication, clean unpublished installations on failure and 
restart, and record mods metrics only after publication. A committed LOAD 
remains successful when source cleanup fails; retained source data keeps its 
sidecars.
   
   Compatibility adaptations use 1.3's synchronous `.mods` and `getModFile` 
APIs, copy-based staging, and TsFile 1.1 tablet/device/schema APIs. The 
source's mods2 conversion changes have no counterpart in 1.3's single-format 
deletion storage. The unit and process-crash tests cover the equivalent 
supported scenarios, including both source deletion policies. Required messages 
are provided in both locales.
   
   Validation:
   - English full-reactor clean test compilation and the subsequent package 
continuation passed; the distribution artifacts required by downstream modules 
were generated successfully.
   - Chinese full-reactor clean package passed with `with-integration-tests`, 
`ClusterIT`, and `with-zh-locale`.
   - LOAD regression unit tests passed: 6 tests, 0 failures, 0 errors, 0 
skipped.
   - LOAD process-crash integration tests passed: 4 tests, 0 failures, 0 
errors, 0 skipped.
   - Spotless and `git diff --check` passed.
   


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