EnricoMi opened a new issue, #44679: URL: https://github.com/apache/arrow/issues/44679
### Describe the bug, including details regarding any error messages, version, and platform. The current precision of `arrow.flight.Timestamp` is OS-dependent: https://github.com/apache/arrow/blob/093655c60783321c786a8e69632f185d37520f4d/cpp/src/arrow/flight/types.h#L83 The precision of `std::chrono::system_clock::time_point` is - microseconds for macOS - 100 nanoseconds for Windows - nanoseconds for Linux https://github.com/apache/arrow/blob/093655c60783321c786a8e69632f185d37520f4d/python/pyarrow/tests/test_flight.py#L1182-L1194 In order to be OS-agnostic, the timestamp resolution should be nanoseconds everywhere. In Python, the equivalent type `TimePoint` is correctly defined with nanoseconds precision for any OS: https://github.com/apache/arrow/blob/093655c60783321c786a8e69632f185d37520f4d/python/pyarrow/src/arrow/python/datetime.h#L88-L89 ### Component(s) C++ -- 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: issues-unsubscr...@arrow.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
