spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dongjoon Hyun (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-18255) SQLContext.getOrCreate always returns a SQLContext even if a user originally created a HiveContext
Date Fri, 16 Dec 2016 23:14:58 GMT

    [ https://issues.apache.org/jira/browse/SPARK-18255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15755762#comment-15755762
] 

Dongjoon Hyun commented on SPARK-18255:
---------------------------------------

Hi, [~yhuai].
I have a question about HiveContext. HiveContext is deprecated in 2.0.0, and Apache Spark
is now 2.1.0.
I guess HiveContext will be removed in 2017. Then, the code related this issue will be removed
together at that them.
Am I correct?

> SQLContext.getOrCreate always returns a SQLContext even if a user originally created
a HiveContext
> --------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-18255
>                 URL: https://issues.apache.org/jira/browse/SPARK-18255
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 2.0.0
>            Reporter: Yin Huai
>
> It is possible that a user creates HiveContext at beginning. However, SQLContext.getOrCreate
will always returns a SQLContext instead of returning a HiveContext. This behavior change
may break user code if {{SQLContext.getOrCreate().asInstanceOf[HiveContext]}} is used. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message