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

Posted to jira@arrow.apache.org by "Ben Kietzman (Jira)" <ji...@apache.org> on 2021/07/14 14:11:00 UTC

[jira] [Updated] (ARROW-13328) [C++][Dataset] Use an ExecPlan for synchronous scans or drop synchronous scans

     [ https://issues.apache.org/jira/browse/ARROW-13328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ben Kietzman updated ARROW-13328:
---------------------------------
    Summary: [C++][Dataset] Use an ExecPlan for synchronous scans or drop synchronous scans  (was: [C++][Dataset] Use an ExecPlan for synchronous scans)

> [C++][Dataset] Use an ExecPlan for synchronous scans or drop synchronous scans
> ------------------------------------------------------------------------------
>
>                 Key: ARROW-13328
>                 URL: https://issues.apache.org/jira/browse/ARROW-13328
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>            Reporter: Ben Kietzman
>            Priority: Major
>              Labels: dataset
>             Fix For: 6.0.0
>
>
> ARROW-13238 ensured that asynchronous dataset scans are internally backed by ExecPlans, allowing easier integration with new ExecNode sinks.
> However synchronous scans are still backed by {{FilterAndProjectScanTask}} and are not consumable using ExecNodes. Ideally, we should route synchronous scans through an ExecPlan as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)