DanielLeens commented on issue #10924:
URL: https://github.com/apache/seatunnel/issues/10924#issuecomment-4498073064
Thanks for the report.
The current stack already narrows this down to the Doris auto-create path
rather than the normal runtime write path:
`DefaultSaveModeHandler.createTable -> DorisCatalog.createTable`
So this looks closer to a schema/type-mapping compatibility issue than a
generic config mistake.
To narrow it down correctly, we still need:
1. the exact Doris version (FE / BE)
because decimal support and validation can differ by Doris version
2. the source MySQL table DDL, or at least the failing decimal column
definitions
so we can see the actual precision / scale coming from CDC
3. the Doris sink config related to auto-create / save mode, and whether a
custom create-table template is being used
so we can tell whether this comes from the default generated DDL or an
overridden template
4. if possible, the generated `CREATE TABLE` SQL or the full DEBUG log
around `DorisCatalog.createTable`
so we can compare the exact decimal definition sent to Doris with the
upstream schema
As a temporary workaround, you can manually create the target Doris table
first with the expected decimal definition, and then rerun the job without
depending on sink-side auto-create.
Once you share the items above, we can confirm whether this is a
SeaTunnel-side bug or a Doris-version-specific compatibility gap much more
precisely.
--
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]
