Caideyipi opened a new pull request, #19113: URL: https://github.com/apache/iotdb/pull/19113
## Description Backport #19096 (814b77028ad42035ae4a8645481d3db84a40f953) to `dev/1.3`, based on c0811e54d01c1f4480d10506930c44d06cfb12e6. Keep row-level time filtering while historical TsFiles are closing, preserve the existing realtime behavior and explicit loose-time-range setting, and retry failed first-reference acquisition without discarding the file or advancing historical progress. ### Backport adaptations - Apply the historical-source changes to `PipeHistoricalDataRegionTsFileSource` and its existing resource set. - Move queue removal after successful event supply, and release the source pin only after the event acquires its reference. The 1.3 source removed queue entries before acquisition, so this ordering adjustment is required to preserve the original retry behavior. - Adapt the six added regression tests to the tree-model constructors and `PlainDeviceID`. Check both source-pin and event-reference directories, which are separate in 1.3. - Define the original exception template in both target locale files because this branch does not yet provide the corresponding message constant. ### Validation - Built the required TsFile version from source, then ran a clean DataNode dependency-reactor test build: **20 tests passed, 0 failures, errors, or skips**, including all six added tests. - Clean English `test-compile`: every Java module compiled successfully. The overall command exited 1 only because the assembly-only `distribution` module requires server/CLI/ConfigNode ZIPs produced during `package`. - Clean Chinese Java-reactor compilation passed: `mvn -T 2 clean test-compile -pl '!distribution' -P with-zh-locale -DskipTests`. - Spotless and message-key/format-placeholder parity checks passed. Source dependencies were built in an isolated verification directory. Enforcer, Checkstyle, and RAT checks were skipped; distribution packaging was not validated. -- 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]
