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

   ## Summary
   
   - add built-in `logical-backup-sink` / `logical-backup-connector` plugins 
that persist Pipe metadata and data events as ordered WAL-like `.pwal` segments
   - add CRC32C/SHA-256 integrity checks, atomic manifests, segment 
recovery/rotation, directory locking, append identity validation, and committed 
event groups
   - support tablet, TsFile, delete, schema plan/snapshot, heartbeat, and 
terminate records for tree and table models
   - add archive inspect/verify/stats/export/import/restore commands with safe 
ZIP handling, dry-run, checkpoints, schema-first replay, and replay request 
allowlisting
   - package Linux and Windows import/export wrappers in the CLI distribution 
and provide English/Chinese messages
   
   ## Validation
   
   - node-commons targeted tests: 32 passed (`LogicalBackupWriterTest`, 
`LogicalBackupArchiveReaderTest`, `BuiltinPipePluginTest`)
   - CLI targeted tests: 4 passed (`PipeLogicalBackupToolTest`)
   - node-commons and CLI install/package validation passed
   - Spotless, Checkstyle, RAT, and forbidden-apis checks passed
   - English and Chinese locale compilation passed for node-commons and CLI
   - distribution packaging passed; the CLI ZIP contains all six wrappers plus 
CLI, node-commons, and Gson JARs
   - verified the CLI JAR contains `PipeLogicalBackupTool` and 
`PipeTransferDataNodeHandshakeV2Req`
   
   ## Known baseline issue
   
   DataNode compile was checked in both English and Chinese locales. Both reach 
the same four existing generated-interface errors in `MPPDataExchangeManager` 
and `DeviceEntryRpcSegmentFetcher`; neither file is modified by this PR, and no 
logical-backup compilation errors are reported.


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