Kevin Crouse created ARROW-16022:
------------------------------------
Summary: floor_temporal / ceil_temporal throws exception for
existing timestamps if ambiguous/existing
Key: ARROW-16022
URL: https://issues.apache.org/jira/browse/ARROW-16022
Project: Apache Arrow
Issue Type: Bug
Components: Python
Affects Versions: 7.0.0
Reporter: Kevin Crouse
Running pyarrow.compute.floor_temporal for timestamps that exist will throw
exceptions if the times are invalid.
As the *_temporal functions do not fundamentally change the times, it does not
make sense that they would fail due to a timezone issue. If they must fail, it
should be when the pyarrow.Timestamp is created.
{code:java}
import pyarrow
import pyarrow.compute as pc
import datetime
t = pyarrow.timestamp('s', tz='America/New_York')
dt = datetime.datetime(2013, 11, 3, 1, 3, 14, tzinfo =
pytz.timezone('America/New_York'))
# if a timestamp must be invalid, this could fail
za = pyarrow.array([dt], t)
# raises an exception, even though this is conceptually an identity function
pc.floor_temporal(za, unit = 'second') {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
