[
https://issues.apache.org/jira/browse/ARROW-13328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17381889#comment-17381889
]
Joris Van den Bossche commented on ARROW-13328:
-----------------------------------------------
bq. On the other hand, we've been using it for a while now and I wouldn't say
we've run into anything major.
I think in the bindings (at least Python, where there is a
{{use_async=False}}), we are still using the sync scanner by default, though.
So while we are running our tests with both the async / sync scanner, I suppose
the async one hasn't seen much "real world" usage by users?
> [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)
