[GitHub] [arrow] danepitkin commented on issue #33321: [Python] Support converting to non-nano datetime64 for pandas >= 2.0

["danepitkin (via GitHub)" <gi...@apache.org>]

danepitkin commented on issue #33321:
URL: https://github.com/apache/arrow/issues/33321#issuecomment-1552166137

   > When users have pandas >= 2, we should support converting with preserving the resolution. We should certainly do so if the pandas metadata indicates which resolution was originally used (to ensure correct roundtrip).
   We could (and at some point also should) also do that by default if there is no pandas metadata (but maybe only later depending on how stable this new feature is in pandas, as it is potentially a breaking change for our users if you use eg pyarrow to read a parquet file).
   
   Can you provide some more detail about this paragraph? Does pandas metadata mean the `pyarrow/array.pxi::PandasOptions` class? When would pandas metadata not be present and why would that break parquet reading?


-- 
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: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org