[
https://issues.apache.org/jira/browse/ARROW-14108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17496066#comment-17496066
]
Rok Mihevc commented on ARROW-14108:
------------------------------------
[~jorisvandenbossche] Thanks for reviewing! I'm not sure how this will get
consumed in the end and how much convenience this kernel brings. Since the
output is a struct I don't really see much of possibility for reuse, but I
might (very likely) just be missing it.
Perhaps an elegant way would be to add _cast(DayTimeBetween) ->
dayhours_between_ and handle this via dispatchBest. I'm not sure how much
overhead that brings.
[~westonpace] could you quantify the convenience gained by having this kernel?
> [C++] interval_between(timestamptz, timestamptz) -> interval kernel
> -------------------------------------------------------------------
>
> Key: ARROW-14108
> URL: https://issues.apache.org/jira/browse/ARROW-14108
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: C++
> Reporter: Weston Pace
> Assignee: Rok Mihevc
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Given two timestamps that each have time zones this function should return an
> interval from the first timestamp to the second timestamp according to the
> following rules (postgres rules):
> * 1 day is 24 physical hours (which may not exactly equal 1 calendar day).
> * Intervals returned will never contain a months/years field
> Examples:
> interval_between('2021-03-14 00:00:00 America/Denver', '2021-03-15 00:00:00
> America/Denver') => { "hours": 23 }
> interval_between('2021-03-14 00:00:00 UTC', '2021-03-15 00:00:00 UTC') => {
> "days": 1}
> interval_between('2021-03-14 00:00:00 UTC', '2020-03-14 00:00:00 UTC') => {
> "days": 365}
> If the first timestamp is larger than the second timestamp then the interval
> will be negative.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
