You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Weston Pace (Jira)" <ji...@apache.org> on 2022/08/24 00:17:00 UTC
[jira] [Created] (ARROW-17509) [C++] Simplify async scheduler by removing the need to call End
Weston Pace created ARROW-17509:
-----------------------------------
Summary: [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
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)