-
Notifications
You must be signed in to change notification settings - Fork 264
Use CUDF's "UNBOUNDED" window boundaries for time-range queries. #1169
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
Use CUDF's "UNBOUNDED" window boundaries for time-range queries. #1169
Conversation
|
@mythrocks you need to update the commit with a signoff |
Signed-off-by: Mithun RK <[email protected]>
064c1b7 to
1d6d130
Compare
This was merged a couple of hours ago. I have rebased the change and signed the commit. |
|
build |
|
An odd test failure: |
|
Looks related to: apache/spark#30432. So |
#1206 has been committed. (Thanks, @jlowe.) I'll try a rebuild. |
|
build |
|
build |
|
build |
Thanks, @sameerz. The builds launched when I rebased seemed to hang as well. It seems to have worked that time. w007! |
Signed-off-by: Mithun RK <[email protected]>
Signed-off-by: Mithun RK <[email protected]>
Fixes #1039. Depends on rapidsai/cudf#6811.
This change aims to allow for unbounded time-range window function queries to return the right results. It depends on the explicit support to specify unbounded window boundaries in CUDF. This cannot be checked in without rapidsai/cudf#6811.