Github user davies commented on the pull request:
https://github.com/apache/spark/pull/9185#issuecomment-154548391
R is does not support threading, it's reasonable that SparkR does not
support multiple sessions in the same R process in the same time, as we move to
have a SQLContext a singleton in SparkR.
Considering two cases:
1) the JVM is launched by R process, then call `new SQLContext` or
`SQLContext.getOrCreate` will be the same.
2) The JVM is launched first, then launch R process and pass the
information of R backend into it. Should SparkR share the same SQL session with
other applications in JVM or not? Then @marmbrus 's suggestion sounds like a
better approach, giving use the ability to choose what they want.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
