[
https://issues.apache.org/jira/browse/ARROW-15798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dragoș Moldovan-Grünfeld updated ARROW-15798:
---------------------------------------------
Summary: [R][C++] Discussion: Should cast_date32 support an origin option?
(was: [R][C++] Discussion: Should the cast_date32 support an origin option?)
> [R][C++] Discussion: Should cast_date32 support an origin option?
> -----------------------------------------------------------------
>
> Key: ARROW-15798
> URL: https://issues.apache.org/jira/browse/ARROW-15798
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++, R
> Reporter: Dragoș Moldovan-Grünfeld
> Priority: Major
>
> Currently the casting from integer to date works, but assumes epoch
> (1970-01-01) as the origin.
> {code:r}
> > a <- Array$create(32L)
> > a$cast(date32())
> Array
> <date32[day]>
> [
> 1970-02-02
> ]
> {code}
> Would it make sense to have an {{origin}} option that would allow the user to
> fine tune the casting? For example, in R the {{base::as.Date()}} function has
> such an argument
> {code:r}
> > as.Date(32, origin = "1970-01-02")
> [1] "1970-02-03"
> {code}
> We have a potential workaround in R (once we support date & duration
> arithmetic), but I was wondering if there might me more general interest for
> this.
> A secondary aspect (as my R example shows) R support casting to date not only
> from integers, but also doubles. Would there be interesting in that? Need be
> I can split this into several tickets.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
