zhangshenghang commented on issue #10034: URL: https://github.com/apache/seatunnel/issues/10034#issuecomment-3742256347
<!-- seatunnel-pr-reviewer --> Thanks for reporting this issue! I've checked the codebase and confirmed that Log engine (including Log, TinyLog, and StripeLog) is actually supported in the ClickHouse sink connector since version 2.3.4 or later. The implementation is in `JdbcBatchStatementExecutorBuilder.isLogFamilyEngine()` (lines 56-64), which explicitly detects these engines and routes them to use simple INSERT-only mode without CDC operations (UPDATE/DELETE are not supported by Log engines). **Likely cause:** The error in your screenshot suggests you may be using an older SeaTunnel version where this support wasn't implemented yet, or the table engine name wasn't detected correctly. **What to check:** 1. Verify your SeaTunnel version is 2.3.4+ (the issue shows "dev" but confirm your actual build) 2. Check the exact engine name in your ClickHouse table: `SELECT engine FROM system.tables WHERE database = 'default' AND table = 'sink_table'` 3. Review SeaTunnel logs for messages about table engine detection **Questions to help diagnose:** - What is your exact SeaTunnel version (`bin/seatunnel --version`)? - What is the output of `SHOW CREATE TABLE default.sink_table` in ClickHouse? - Can you share the full error message from the SeaTunnel logs? The issue is marked as closed, so if you're still experiencing this on the latest version, please provide the above details. -- 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]
