Dandandan opened a new issue, #628: URL: https://github.com/apache/arrow-ballista/issues/628
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.** In presence of a limit, Ballista could cancel / remove the remaining (both active/inactive) tasks once the total number of rows exceeds the limit. **Describe the solution you'd like** For each stage, add an optional `limit`. The query stage scheduler could track the total number of rows, based on the task metrics and update the number of rows accordingly. It could cancel the remaining tasks and continue with the next stage. **Describe alternatives you've considered** **Additional context** -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
