[
https://issues.apache.org/jira/browse/SPARK-15037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15265256#comment-15265256
]
Dongjoon Hyun edited comment on SPARK-15037 at 4/30/16 9:08 AM:
----------------------------------------------------------------
Hi, [~rxin].
Until now, it seems there are two issues.
- `object SQLContext` has still its own unique functions. We cannot replace
`SQLContext` completely because `SharedSQLContext` uses it. Also,
`MLlibTestSparkContext` does.
- Constructor `SparkSession(JavaSparkSession)` or `JavaSparkSession` class is
needed for Java testsuite.
We had better handle them as separate issues before this kind of refactoring
issue. How do you think about this?
was (Author: dongjoon):
Hi, [~rxin].
Until now, it seems there are two issues.
- `object SQLContext` has still its own unique functions. We cannot replace
`SQLContext` completely because `SharedSQLContext` uses it. Also,
`MLlibTestSparkContext` does.
- Also, constructor `SparkSession(JavaSparkSession)` or `JavaSparkSession`
class is needed for Java testsuite.
We had better handle them as separate issues before this kind of refactoring
issue. How do you think about this?
> Use SparkSession instread of SQLContext in testsuites
> -----------------------------------------------------
>
> Key: SPARK-15037
> URL: https://issues.apache.org/jira/browse/SPARK-15037
> Project: Spark
> Issue Type: Test
> Reporter: Dongjoon Hyun
>
> This issue aims to update the existing testsuites to use `SparkSession`
> instread of `SQLContext` since `SQLContext` exists just for backward
> compatibility.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
