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

   ## Description
   
   When Active LOAD scans a table-model TsFile while schema regions report 
`NO_AVAILABLE_REGION_GROUP`, device schema validation can turn that status into 
a permanent `LOAD_FILE_ERROR`. The active loader then moves the file to the 
failure directory, preventing automatic recovery.
   
   Preserve `NO_AVAILABLE_REGION_GROUP` through direct and wrapped 
runtime/checked exceptions so the analyzer returns 
`LOAD_TEMPORARY_UNAVAILABLE_EXCEPTION`. For example, a pending table-model file 
that fails schema validation during recovery now stays pending and can be 
analyzed again from the same unchanged file once regions become available. 
Metadata and permission errors retain their existing terminal behavior.
   
   Add regression tests for direct/wrapped region-unavailability errors, 
recovery with a fresh analyzer, unchanged input bytes, and permanent 
metadata/permission errors. A persistently unavailable region still requires 
operator intervention; the status does not distinguish it from a recovering 
region.
   
   ## Validation
   
   - Spotless passed.
   - Clean-reactor targeted tests passed locally: 35 tests, no failures, 
errors, or skips. All newly added tests were run locally.
   
   ```bash
   mvn -B -ntp clean test -pl iotdb-core/datanode -am 
-Dtest=LoadTsFileTableSchemaRecoveryTest,LoadTsFileAnalyzerDiagnosticsTest,ActiveLoadFailedMessageHandlerTest,ActiveLoadTsFileLoaderTest
 -Dsurefire.failIfNoSpecifiedTests=false -Dmaven.build.cache.enabled=false 
-Dstyle.color=never
   ```
   
   The archived two-cluster receiver-restart integration test was not rerun. 
The new recovery test covers successful reanalysis, not a live cluster restart.
   
   This PR has:
   
   - [x] been self-reviewed.
   - [x] added comments explaining the intent of the exception handling.
   - [x] added unit tests covering the changed behavior.


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