DanielLeens commented on issue #12841: URL: https://github.com/apache/seatunnel/issues/12841#issuecomment-6233674134
Thank you for separating this from the Spark-specific work in #12814. The current `dev` paths do clamp signed MySQL DECIMAL values above 38 to `DECIMAL(38, 18)`, while the unsigned path retains a different precision rule; that is a real JDBC schema-mapping defect and can lose integer as well as fractional capacity. Please open a focused PR rather than applying the same change broadly without evidence. At minimum, cover MySQL `DECIMAL(65,0)` and `DECIMAL(50,30)` through source schema discovery and MySQL sink DDL/value flow; state the intended rule for unsigned values; and treat OceanBase and GenericTypeConverter as separate, reproduced contracts unless their tests establish the same behavior. Link the Spark representation boundary to #12814, and document any observable schema-compatibility change. Classification: A — JDBC / MySQL DECIMAL schema mapping. -- 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]
