-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[R] Compatibility of arrow with dplyr 1.1.0 #14947
Comments
Thanks for the heads up @lionel-! The arrow 11.0.0 release is planned for ~ 16th of January, so we should (:crossed_fingers: ) be able to integrate these changes in 11.0.0 |
I just saw your PR, awesome 🚀 |
paleolimbot
added a commit
that referenced
this issue
Dec 26, 2022
Each commit in this PR fixes a breaking/behaviour change described in #14947. I could not build the dev version of arrow so this is only tested against the CRAN version. Also there might be changes introduced since the last release that require compatibility adjustments. Could someone pick this up from here please? Closes #14947. * Closes: #14947 Lead-authored-by: Lionel Henry <[email protected]> Co-authored-by: Dewey Dunnington <[email protected]> Co-authored-by: Dewey Dunnington <[email protected]> Signed-off-by: Dewey Dunnington <[email protected]>
EpsilonPrime
pushed a commit
to EpsilonPrime/arrow
that referenced
this issue
Jan 5, 2023
Each commit in this PR fixes a breaking/behaviour change described in apache#14947. I could not build the dev version of arrow so this is only tested against the CRAN version. Also there might be changes introduced since the last release that require compatibility adjustments. Could someone pick this up from here please? Closes apache#14947. * Closes: apache#14947 Lead-authored-by: Lionel Henry <[email protected]> Co-authored-by: Dewey Dunnington <[email protected]> Co-authored-by: Dewey Dunnington <[email protected]> Signed-off-by: Dewey Dunnington <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug, including details regarding any error messages, version, and platform.
dplyr 1.1.0 is planned for January 27 and includes breaking/behaviour changes that need to be addressed in arrow:
n_distinct()
no longer accepts zero argumentsunion_all()
now requires compatible argumentsdistinct()
now returns cols in supplied orderacross()
now requires an argumentsemi_join()
andanti_join()
are stricter with unexpected arguments. Causes an issue in tests withkeep
.slice_min()
andslice_max()
now requireorder_by
We plan to release on January 27. A pre-emptive release to fix the above would be helpful.
Component(s)
R
The text was updated successfully, but these errors were encountered: