[
https://issues.apache.org/jira/browse/ARROW-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17421606#comment-17421606
]
Jonathan Keane commented on ARROW-8379:
---------------------------------------
Overall this sounds good and in line with what I've been experiencing. A few
comments on specific points (in no particular order):
> just decreases the frequency of deadlock.
I suspect this is true — with my work on DuckDB I had a similar experience
where fewer threads meant fewer opportunities to deadlock (and not that it was
fixed by some number greater than 1).
> On 32-bit Rtools 3.5 disabling datasets
I don't have a better solution, but part of me wonders if there's much of a
point to install Arrow if one doesn't have datasets enabled (this would include
basically any dplyr on tables as well, right?) Maybe it's time to end support
for this (though that's earlier than I think is typical / we strive for!). At
least, maybe we should include a message that says something like "32bit
windows 3.5 has substantially reduced functionality, please consider upgrading
your R to take full advantage of..."
> [R] Investigate/fix thread safety issues (esp. Windows)
> -------------------------------------------------------
>
> Key: ARROW-8379
> URL: https://issues.apache.org/jira/browse/ARROW-8379
> Project: Apache Arrow
> Issue Type: New Feature
> Components: R
> Reporter: Neal Richardson
> Priority: Major
>
> There have been a number of issues where the R bindings' multithreading has
> been implicated in unstable behavior (ARROW-7844 for example). In ARROW-8375
> I disabled {{use_threads}} in the Windows tests, and it appeared that the
> mysterious Windows segfaults stopped. We should fix whatever the underlying
> issues are.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
