-
Notifications
You must be signed in to change notification settings - Fork 232
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
Support Retry for GpuLocalLimitExec and GpuGlobalLimitExec #9193
Conversation
Signed-off-by: Firestarman <firestarmanllc@gmail.com>
build |
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.
Just a small nit
} | ||
} | ||
|
||
def apply( |
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.
nit: could we call this something different. To me GpuBaseLimitExec.apply should return a GpuBaseLimitExec, we are not 100% consistent about that. Could we rename the object to GpuBaseLimitExecIterator
? It would make it a little clearer.
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.
Updated. I changed the new object "GpuBaseLimitExec" to a class called GpuBaseLimitIterator
.
Signed-off-by: Firestarman <firestarmanllc@gmail.com>
build |
close #8315
This PR adds the retry support to the processing of slicing the batch (in
sliceBatchAndCloseWithRetry
function) used by bothGpuLocalLimitExec
andGpuGlobalLimitExec
.It also does some refactor by moving the code of the output iterator to a new iterator named
GpuBaseLimitIterator
, then we can test the core logic by unit tests.