[
https://issues.apache.org/jira/browse/ARROW-17509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Weston Pace resolved ARROW-17509.
---------------------------------
Fix Version/s: 11.0.0
Resolution: Fixed
Issue resolved by pull request 14524
[https://github.com/apache/arrow/pull/14524]
> [C++] Simplify async scheduler by removing the need to call End
> ---------------------------------------------------------------
>
> Key: ARROW-17509
> URL: https://issues.apache.org/jira/browse/ARROW-17509
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Reporter: Weston Pace
> Priority: Major
> Labels: pull-request-available
> Fix For: 11.0.0
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> Right now the AsyncScheduler requires that we call End. This is to
> distinguish between a scheduler running out of tasks because it hit an idle
> period (in which case it shouldn't mark itself finished) and a scheduler
> running out of tasks because it is truly done (in which case it should mark
> itself finished).
> It should be possible to require that scheduler tasks only be added by
> existing tasks. When creating a scheduler one would supply an "initial task"
> to bootstrap the first set of tasks. In this case we could get rid of the
> End method because the only time a scheduler will run out of tasks is when it
> is finished.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
