[
https://issues.apache.org/jira/browse/ARROW-14266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461650#comment-17461650
]
Weston Pace commented on ARROW-14266:
-------------------------------------
I think {{write_dataset}}'s first argument changes from {{dataset}} to
{{dataset_or_whatever_we_call_a_dplyr_query}} and then if it is a dataset keep
the existing logic but if it is the other thing then slap a write node on the
end and call something like {{do_exec_plan}}
> [R] Use WriteNode to write queries
> ----------------------------------
>
> Key: ARROW-14266
> URL: https://issues.apache.org/jira/browse/ARROW-14266
> Project: Apache Arrow
> Issue Type: Improvement
> Components: R
> Reporter: Neal Richardson
> Priority: Major
> Labels: query-engine
> Fix For: 7.0.0
>
>
> Following ARROW-13542. Any query that has a join or an aggregation currently
> has to first evaluate the query and hold it in memory before creating a
> Scanner to write it. We could improve that by using a WriteNode inside
> write_dataset() (and maybe that improves the other cases too, or at least
> allows us to delete some code).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
