You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2022/05/12 12:50:29 UTC

[GitHub] [arrow] jorisvandenbossche commented on pull request #12528: ARROW-15251: [C++] Temporal floor/ceil/round handle ambiguous/nonexistent local time

jorisvandenbossche commented on PR #12528:
URL: https://github.com/apache/arrow/pull/12528#issuecomment-1124954128

   I was also just trying my example of above (https://github.com/apache/arrow/pull/12528#issuecomment-1055262792) that results in a non-existing time. But now that actually returns something instead of erroring:
   
   ```
   In [21]: arr = pc.assume_timezone(pa.array([pd.Timestamp("2015-03-29 02:30:00")]), "Europe/Brussels", nonexistent="latest")
       ...: pc.round_temporal(arr, 16, "minute")
   Out[21]: 
   <pyarrow.lib.TimestampArray object at 0x7f62c8fc7e80>
   [
     2015-03-29 01:08:00.000000
   ]
   ```
   
   I am not fully sure that is correct? Previously it tried to round in naive time and then gave "2015-03-29 02:56:00", which doesn't exist. But I don't see how we would get to the result above (which is "2015-03-29 03:08:00" in local naive time)
   


-- 
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