suntectec commented on issue #10099: URL: https://github.com/apache/paimon/issues/10099#issuecomment-5865243895
Thanks @zhang-arvin for the detailed analysis. I agree the core issue is the silent truncation, not the lack of nanosecond support. Extending TIME to precision 4–9 would mean changing the internal representation from int to long across Flink, Paimon, and Parquet — a large cross-cutting change, as FLINK-39214 shows. Given that TIMESTAMP(9) already covers most high-precision needs, I lean towards fixing the silent truncation rather than expanding the type system. PR #10200's approach — making the declared precision match what is actually stored, so unsupported precision fails fast — seems like a practical path forward. It addresses the correctness issue without the cost of a full storage-format change. Just my two cents. Happy to hear other perspectives. -- 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]
