clxstart opened a new pull request, #17891: URL: https://github.com/apache/iotdb/pull/17891
## Summary Pipe replication currently fails when `data.delete` is included in the source configuration for table mode, causing the pipe to enter STOP state instead of continuing to synchronize. The fix updates the delete-event transfer and receiver handling so delete operations are treated as supported replication data, applied safely on the sink side, and downgraded to recoverable handling when a specific delete cannot be applied. ## Changes - Normalize pipe delete-event payloads before transfer so table-mode delete data preserves the needed range and path metadata without assuming tsfile-only semantics. - Update batch/request building to carry `data.delete` events through the pipe pipeline instead of rejecting them or turning malformed payloads into fatal errors. - Adjust the thrift receiver to apply delete requests as a valid replication operation and return recoverable status for target-specific delete failures instead of stopping the pipe. - Add regression coverage for a pipe configured with `inclusion='data.insert,data.delete'` that deletes data in table mode and verifies the pipe remains RUNNING and the sink reflects the deletion. ## Validation - Test commands: none were provided or runnable in the issue context; status pending. - Baseline results: not executed, so no pass/fail result is available yet. - Pending validation: run the new integration test for table-mode `data.insert,data.delete` replication and confirm the pipe stays RUNNING after delete operations. - Pending validation: manually verify source-to-sink deletion replication to ensure there are no retries, duplicates, or STOP-state transitions. ## Risks - The exact delete-event and receiver classes may differ slightly in the target branch, so file-level adjustments may be needed during implementation. - Delete semantics may differ between table mode and timeseries mode, so the fix must avoid changing existing behavior for other pipe replication paths. -- 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]
