You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Michael Armbrust (JIRA)" <ji...@apache.org> on 2014/08/12 05:09:11 UTC

[jira] [Resolved] (SPARK-2844) Existing JVM Hive Context not correctly used in Python Hive Context

     [ https://issues.apache.org/jira/browse/SPARK-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Armbrust resolved SPARK-2844.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.1.0

> Existing JVM Hive Context not correctly used in Python Hive Context
> -------------------------------------------------------------------
>
>                 Key: SPARK-2844
>                 URL: https://issues.apache.org/jira/browse/SPARK-2844
>             Project: Spark
>          Issue Type: Bug
>          Components: PySpark, SQL
>            Reporter: Ahir Reddy
>            Assignee: Ahir Reddy
>             Fix For: 1.1.0
>
>
> Unlike the SQLContext, assing an existing JVM HiveContext object into the Python HiveContext constructor does not actually re-use that object. Instead it will create a new HiveContext.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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