[
https://issues.apache.org/jira/browse/ARROW-14663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17442192#comment-17442192
]
Dragoș Moldovan-Grünfeld commented on ARROW-14663:
--------------------------------------------------
Probably not a huge amount of value (besides keeping up with the readr
signature). I think using the global thread pool in
{{CsvWriteOptions$create()}} would go a long way even if not directly exposed
to the user. Maybe we can allow the use to specify {{write_options}} or
{{readr_options}} and that will allow them some level of control over the use
of the global thread pool.
> [R] Expose number of threads in read_csv_arrow() and write_csv_arrow()
> ----------------------------------------------------------------------
>
> Key: ARROW-14663
> URL: https://issues.apache.org/jira/browse/ARROW-14663
> Project: Apache Arrow
> Issue Type: Improvement
> Components: R
> Reporter: Dragoș Moldovan-Grünfeld
> Priority: Minor
>
> As of {{readr}} 2.0.0 (and the switch to {{vroom}}) both {{read_csv()}} and
> {{write_csv()}} allow the user to pass the number of threads to be used when
> processing (the {{num_threads}} argument). Currently this functionality is
> not exposed in Arrow. Some functionality (not yet the CSV read or write)
> allows the user to use the global CPU thread pool, but {{num_threads}} would
> offer more granular control.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
