zhang-arvin commented on issue #10099: URL: https://github.com/apache/paimon/issues/10099#issuecomment-5841785075
@zhang-arvin here — I'd like to take this one. Root cause is clear from the report: a high-precision time value gets narrowed to int milliseconds-of-day somewhere in the connector type mapping, so `MSSQL TIME(7)` (`12:34:56.1234567`) is rounded up to millisecond precision before it reaches Parquet `TIME-MILLIS`. Plan: 1. Locate the time conversion in the MSSQL/Paimon type mapping path and check whether the precision loss is unconditionally baked in (int ms-of-day) or whether a higher-precision target exists for the requested type. 2. Fix the conversion so precision is not silently discarded, or fail loudly if the target type genuinely cannot represent it — rather than rounding without notice. 3. Add a regression test asserting the written/read round-trip preserves the sub-millisecond digits that the target type supports. Please assign this to me if convenient. -- 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]
