DanielLeens commented on issue #10850: URL: https://github.com/apache/seatunnel/issues/10850#issuecomment-4402594200
Thanks for reporting this. After checking the current JDBC sink path, I cannot confirm a generic SeaTunnel bug from the current information yet. This reads more like a boundary between expected DM column behavior and a possible enhancement for very large text handling: - the generic JDBC writer currently binds STRING values through `PreparedStatement#setString(...)` - the DM dialect does distinguish normal string columns (`VARCHAR/VARCHAR2`) from large-text types such as `TEXT/CLOB` - so if the target column is still length-limited `VARCHAR/VARCHAR2`, a "string truncation" error is expected from the database itself If your expectation is that SeaTunnel should automatically switch oversized strings to a CLOB/TEXT-style write path, that would be a new enhancement rather than a confirmed existing bug. To narrow this down, we still need: 1. SeaTunnel version 2. full JDBC sink config, with sensitive values masked 3. target table DDL, especially the exact type of the failing column 4. whether the table was pre-created or created by SeaTunnel 5. an example payload size or a minimal reproduction Also, since SeaTunnel issue discussion is handled in English, please update the issue description in English when you have a moment. That will make it easier for more contributors to help review it. Once we have the DDL and config, we can tell whether this is a target-column configuration problem or a missing DM large-text feature in SeaTunnel. -- 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]
