GH-44679: [C++][Python] Fix Flight Timestamp precision, revert workaround from #43537 #44681
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes are included in this PR?
Make
arrow.flight.Timestamp
nanoseconds precision and OS-independent.Use the
CTimePoint
forFlightEndpoint.expiration_time
to have OS-independent nanoseconds precision.arrow/python/pyarrow/includes/libarrow_flight.pxd
Lines 133 to 139 in 093655c
This reverts workaround for
expiration_time
from #43537.Are these changes tested?
Existing unit tests are adjusted to the new precision.
Are there any user-facing changes?
This PR includes breaking changes to public APIs.
The values of
FlightEndpoint.expiration_time
now have nanoseconds precision on any operating system.arrow.flight.Timestamp
is OS-dependent #44679