[
https://issues.apache.org/jira/browse/ARROW-17132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17569011#comment-17569011
]
Neal Richardson commented on ARROW-17132:
-----------------------------------------
The assertion is failing on "time", your input variable, not the result of
{{{}yday(){}}}. I don't recall exactly what all of the corners are around
timezones in the R <–> Arrow conversion but I know there are several,
[~dragosmg] may know better. There may be a more stable way of generating your
input data.
> [R] Mutate in compare_dplyr_binding returns wrong type
> ------------------------------------------------------
>
> Key: ARROW-17132
> URL: https://issues.apache.org/jira/browse/ARROW-17132
> Project: Apache Arrow
> Issue Type: Bug
> Components: R
> Reporter: Rok Mihevc
> Priority: Minor
> Labels: test
>
> The following:
> {code:r}
> df <- tibble::tibble(
> time = as.POSIXct(seq(as.Date("1999-12-31", tz = "UTC"),
> as.Date("2001-01-01", tz = "UTC"), by = "day"))
> )
> compare_dplyr_binding(
> .input %>%
> mutate(x = yday(time)) %>%
> collect(),
> df
> )
> {code}
> Fails with:
> {code:bash}
> Failure (test-dplyr-funcs-datetime.R:574:3): extract wday from timestamp
> `object` (`actual`) not equal to `expected` (`expected`).
> `attr(actual$time, 'tzone')` is a character vector ('UTC')
> `attr(expected$time, 'tzone')` is absent
> Backtrace:
> 1. arrow:::compare_dplyr_binding(...)
> at test-dplyr-funcs-datetime.R:574:2
> 2. arrow:::expect_equal(via_batch, expected, ...)
> at tests/testthat/helper-expectation.R:115:4
> 3. testthat::expect_equal(...)
> at tests/testthat/helper-expectation.R:42:4
> {code}
> This also happens for qday and probably other functions where input is
> temporal and output is numeric.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
