You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Alessandro Molina (Jira)" <ji...@apache.org> on 2021/10/01 07:18:07 UTC
[jira] [Updated] (ARROW-12091) [C++] Allow AddCallback/Then to take
in an optional Executor.
[ https://issues.apache.org/jira/browse/ARROW-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alessandro Molina updated ARROW-12091:
--------------------------------------
Fix Version/s: (was: 6.0.0)
7.0.0
> [C++] Allow AddCallback/Then to take in an optional Executor.
> -------------------------------------------------------------
>
> Key: ARROW-12091
> URL: https://issues.apache.org/jira/browse/ARROW-12091
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Reporter: Weston Pace
> Priority: Major
> Fix For: 7.0.0
>
>
> Right now `Executor::Transfer` isn't perfectly reliable since callbacks added after the future has been completed will be run synchronously and so the thread task would be spawned at the wrong time. With this feature `Executor::Transfer` could be fixed.
> This would need to be added to both `Then` and `AddCallback`.
> Ideally the methods would detect if the current thread is already on the desired executor and do nothing in that situation. Spinning up unnecessary thread tasks would do more harm than good.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)