Github user sun-rui commented on a diff in the pull request:
https://github.com/apache/spark/pull/13635#discussion_r67384711
--- Diff: R/pkg/NAMESPACE ---
@@ -6,10 +6,15 @@ importFrom(methods, setGeneric, setMethod, setOldClass)
#useDynLib(SparkR, stringHashCode)
# S3 methods exported
+export("sparkR.session.getOrCreate")
--- End diff --
while SparkSession is the main entry, SparkContext does remain. My thoughts
are:
1. Keep sparkR.init() as is. It still returns the SparkContext.
2. Add new API like SparkRSession.init(), and sparkRSession.stop().
SparkRSession.init() has two forms:
A. it can accept a SparkContext as a parameter, and no other Spark
Configurations.
B. Just like the current sparkR.session.getOrCreate(), it internally
creates SparkContext.
3. Keep sparkRSQL.init() and sparkRHive.init() for backward compatibility,
while they are updated to call SparkRSession.init().
---
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]
