suntectec commented on issue #9621: URL: https://github.com/apache/paimon/issues/9621#issuecomment-5866978054
Thanks for looking into this @LuciferYang. Since the numeric epoch-string path intentionally supports only the standard units (second/milli/micro/nano → precision 0/3/6/9), and testInvalidPrecisions has deliberately treated 1/2/4/5/7/8 as unsupported since #5710, this is currently working as designed rather than a bug. Formatted timestamp strings already parse fine at those precisions. Following the maintainer's note on #9622, it would take a concrete producer/ingestion scenario plus an agreed input-unit contract (and an end-to-end test) to justify generalizing this. Without such a use case, I don't think we should push the PR forward — suggest we close this as won't-fix for now, and reopen if a real scenario shows up. -- 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]
