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

   ## Description
   
   Follow up on #18307: a TsFile containing a segmented device ID such as 
`["root", ""]` must report an invalid path. The schema error could be wrapped 
or routed into tablet conversion, where scan/query corruption recovery could 
swallow the original error and return `LOAD_FILE_ERROR` without a message.
   
   Preserve invalid paths as permanent LOAD errors and reuse device-node 
validation during schema analysis and tablet conversion, including when 
automatic schema creation or schema verification is disabled. Validate null 
nodes before they become the literal `null` in a device string. Path errors 
also bypass corruption recovery in both parsers.
   
   Valid TsFiles continue to ignore malformed legacy database names such as 
`root.`. The regression coverage retains node-based database-prefix matching 
and verifies that a valid device can still use its database after filtering 
legacy entries.
   
   ## Validation
   
   24 focused tests pass with the default locale and `-P with-zh-locale`:
   
   ```text
   mvn -nsu -pl iotdb-core/datanode -am test 
-Dtest=LoadTsFileAnalyzerTest,LoadTsFileInvalidPathTest,LoadTreeStatementDataTypeConvertExecutionVisitorTest
 -Dsurefire.failIfNoSpecifiedTests=false
   ```
   
   Coverage includes empty/null device nodes, a neighboring `.resource` file, 
disabled schema checks, direct tablet conversion, parser-memory release, legacy 
database filtering, and the existing recovery tests for corrupted chunks. Test 
fixtures are generated locally.
   
   - [x] Self-reviewed.
   - [x] Added regression tests and retained existing corruption-recovery tests.
   - [x] Ran Spotless and the DataNode reactor checks.
   


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