avantgardnerio commented on issue #7958: URL: https://github.com/apache/arrow-datafusion/issues/7958#issuecomment-1785271201
Parquet has a proper Timestamp field, correct? https://learn.microsoft.com/en-us/common-data-model/sdk/parquet-to-cdm-datatype And that datatype supports a `precision` field which specifies millis/micros/nanos? So I presume this error only happens when reading an `INT` field and casting? If so, I'd 100% be on board copying the behavior of these other well known databases. Folks who stored their data properly as `Timestamp`s shouldn't be affected. It would be a breaking change to those who just stored as an `INT`, but I think now is the time to make that change since datetime support is relatively new... it will only get harder to change going forward. -- 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]
