You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@seatunnel.apache.org by "DanielLeens (via GitHub)" <gi...@apache.org> on 2026/07/22 01:08:56 UTC

Re: [I] [Bug] Synchronizing data from MySQL 5.7 to PostgreSQL 14 may cause precision loss. [seatunnel]

DanielLeens commented on issue #10198:
URL: https://github.com/apache/seatunnel/issues/10198#issuecomment-5040695822

   I re-read the full thread and the new fix direction. This no longer looks like only a MySQL `FLOAT` explanation.
   
   MySQL `FLOAT` is approximate, but the important symptom here is that after an explicit SQL-side `CAST` / `ROUND` to `DECIMAL`, SeaTunnel still ends up emitting values like `126.555496` in the batch path. That means the decimal result is being pushed back through a lossy float-like path after the query result is materialized, which is a real bug for explicit decimal casts.
   
   PR #11523 is now open to preserve the intended decimal value instead of reformatting it through a lossy conversion path. Let's keep this issue open until that fix is reviewed and validated against both the batch-SQL case and the CDC-shaped case discussed in this thread.
   
   For future issue updates, please prefer English if possible so more community contributors can help directly.


-- 
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: commits-unsubscribe@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org