JingsongLi commented on PR #9622: URL: https://github.com/apache/paimon/pull/9622#issuecomment-5613745249
Closing the current proposal because it introduces six additional numeric epoch-unit conventions without establishing a user requirement for those semantics. A valid TIMESTAMP precision of 0..9 does not by itself establish how an integer string should be interpreted. The existing numeric conversion deliberately accepts seconds/milliseconds/microseconds/nanoseconds (0/3/6/9), and testInvalidPrecisions has explicitly rejected 1/2/4/5/7/8 since #5710; formatted timestamp strings already take the parsing path at those precisions. The default-value path is real, but the new tests prove the chosen power-of-ten formula rather than justify interpreting input in deciseconds, centiseconds, 100-microsecond, 10-microsecond, 100-nanosecond and 10-nanosecond units. Please reopen with a concrete producer/ingestion scenario, an agreed input-unit contract and an end-to-end default-value or ingestion test that verifies the intended instant. -- 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]
