hudi-bot opened a new issue, #14995: URL: https://github.com/apache/hudi/issues/14995
As of now, if a field with timestamp datatype w/ microsec precision is ingested to hudi, resultant dataset will only have until millisec granularity. Ref issue: [https://github.com/apache/hudi/issues/3429] We might need to support microsecs granularity. References issue has some pointers on how to go about it. ## JIRA info - Link: https://issues.apache.org/jira/browse/HUDI-3216 - Type: Improvement - Fix version(s): - 1.1.0 --- ## Comments 12/Jan/22 03:34;chenxiang; I've noticed that flink recently submitted a related pr [hudi-flink support timestamp-micros|https://issues.apache.org/jira/browse/HUDI-3184] Should we move the PR to the common package level in hudi to solve the problem uniformly?;;; --- 13/Jan/22 22:13;shivnarayan;[~chenxiang] : yes, that sounds like a good idea. Do you think you have cycles to take it up. ;;; --- 22/Jan/22 17:07;h7kanna;Hi team, Need confirmation if this will have impact if the timestamp in microseconds is used for source ordering field?;;; --- 24/Jan/22 13:09;shivnarayan;may be. if you have records which just differs in the microsecond part of the timestamp field which is set as your source ordering field (or precombine field), you may see some inconsistencies.;;; -- 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]
