You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Davies Liu (JIRA)" <ji...@apache.org> on 2015/11/19 19:30:11 UTC
[jira] [Updated] (SPARK-11783) When deployed against remote Hive
metastore, HiveContext.executionHive points to wrong metastore
[ https://issues.apache.org/jira/browse/SPARK-11783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davies Liu updated SPARK-11783:
-------------------------------
Priority: Critical (was: Blocker)
> When deployed against remote Hive metastore, HiveContext.executionHive points to wrong metastore
> ------------------------------------------------------------------------------------------------
>
> Key: SPARK-11783
> URL: https://issues.apache.org/jira/browse/SPARK-11783
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 1.5.1, 1.6.0, 1.7.0
> Reporter: Cheng Lian
> Assignee: Cheng Lian
> Priority: Critical
>
> When using remote metastore, execution Hive client somehow is initialized to point to the actual remote metastore instead of the dummy local Derby metastore.
> To reproduce this issue:
> # Configuring {{conf/hive-site.xml}} to point to a remote Hive 1.2.1 metastore.
> # Set {{hive.metastore.uris}} to {{thrift://localhost:9083}}.
> # Start metastore service using {{$HIVE_HOME/bin/hive --service metastore}}
> # Start Thrift server with remote debugging options
> # Attach the debugger to the Thrift server driver process, we can verify that {{executionHive}} points to the remote metastore rather than the local execution Derby metastore.
--
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