-
Notifications
You must be signed in to change notification settings - Fork 924
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
Deprecate cudf::grouped_time_range_rolling_window #17589
Deprecate cudf::grouped_time_range_rolling_window #17589
Conversation
Thank you, @wence-. I've been dragging my feet on this one. I have checked. It appears that I've already removed references to the time-range version of these calls from the Java API, and switched it to numeric ranges.
This is looking good to go. |
The failures seem to be transient and unrelated to the change.
I've restarted the failing CI jobs. |
6e6b5b4
to
3bb751d
Compare
Since the range-based rolling window APIs were extended to support any orderable column (rather than just time-based windows), this function has been a thin forwarding wrapper to cudf::grouped_range_rolling_window. It could have been deprecated at the time, but was not. It seems there are no usages outside of the libcudf test suite. Partially addresses rapidsai#13050.
3bb751d
to
f5366e5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. thanks for working on this!
/merge |
Description
Since the range-based rolling window APIs were extended to support any orderable column (rather than just time-based windows), this function has been a thin forwarding wrapper to
cudf::grouped_range_rolling_window. It could have been deprecated at the time, but was not. It seems there are no usages outside of the libcudf test suite.
Partially addresses #13050.
Checklist