[
https://issues.apache.org/jira/browse/SPARK-11783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953647#comment-15953647
]
Jonathan Maron commented on SPARK-11783:
----------------------------------------
I am running a spark job and, when instantiating a HiveContext, I see that the
client creates a local derby-based metastore. Is this the intent for client
processes? I don't understand the necessity for a client process to create a
metastore instance rather than leverage the remote metastore server.
> 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
> Reporter: Cheng Lian
> Assignee: Cheng Lian
> Priority: Critical
> Fix For: 1.6.0
>
>
> 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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
