You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@arrow.apache.org by "Weston Pace (Jira)" <ji...@apache.org> on 2022/07/22 02:10:00 UTC

[jira] [Created] (ARROW-17180) [C++] Backpressure should resume as a new task, assuming executor is present

Weston Pace created ARROW-17180:
-----------------------------------

             Summary: [C++] Backpressure should resume as a new task, assuming executor is present
                 Key: ARROW-17180
                 URL: https://issues.apache.org/jira/browse/ARROW-17180
             Project: Apache Arrow
          Issue Type: Improvement
          Components: C++
            Reporter: Weston Pace


As brought up on the mailing list: https://lists.apache.org/thread/hscjqyw7lpt95vlkzoslm6pyhy9x6wso

When we resume producing in the source node, we should run the continuation (which starts scanning again) as a new task.  This will avoid potential stack overflow (if we pause and start many times) and help make for more understandable stack traces.  The continuation is unlikely to have anything to do with the task that is calling resume and so there is not as much downside to a context switch.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)