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

   ## Description
   
   Several write-path failure handlers log only the exception message, losing 
the stack trace and nested causes needed to diagnose failed writes. Preserve 
the original exceptions in batch-row execution, ConfigNode table-schema lookup, 
WAL metadata reads and recovery, and file-time-index cache I/O logs.
   
   Also fix the WAL recovery warning's node field: it previously printed the 
exception message where the WAL node identifier belonged. It now reports the 
node directory name and retains the exception as the cause.
   
   Add a regression test that captures a failed batch insert's log event, 
checks that it contains the exception, and verifies the returned status code 
and message.
   
   ## Validation
   
   - `mvn -nsu spotless:apply -pl iotdb-core/datanode`
   - `mvn -nsu test -pl iotdb-core/datanode -Dtest=DataExecutionVisitorTest 
-DfailIfNoTests=false` (English; 1 test passed)
   - `mvn -nsu test-compile -pl iotdb-core/datanode -am -DskipTests` (English; 
28 modules passed)
   - `mvn -nsu test -pl iotdb-core/datanode -am -P with-zh-locale 
-Dtest=DataExecutionVisitorTest -Dsurefire.failIfNoSpecifiedTests=false 
-DfailIfNoTests=false` (Chinese; 28 modules and 1 test passed)
   
   - [x] Self-reviewed.
   - [x] Added a regression test for exception retention and the returned error 
status.
   


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