Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/18281
One comment about putting parallelism in a trait vs. not: Would we want to
avoid creating a "threadpool" when parallelism = 1? In that (common) case,
maybe we'd want to avoid par collections. If so, then the trait could provide
a helper method which takes a range/seq and a function accepting values from
that range. That helper could use par collections or not, depending on the
setting of parallelism. Good, or too complex?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
