[
https://issues.apache.org/jira/browse/SPARK-11208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Armbrust resolved SPARK-11208.
--------------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
Issue resolved by pull request 9178
[https://github.com/apache/spark/pull/9178]
> Filter out 'hive.metastore.rawstore.impl' from executionHive temporary config
> -----------------------------------------------------------------------------
>
> Key: SPARK-11208
> URL: https://issues.apache.org/jira/browse/SPARK-11208
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 1.5.1, 1.6.0
> Reporter: Artem Aliev
> Fix For: 1.6.0
>
>
> Spark use two hive meta stores: external one for storing tables and internal
> one (executionHive):
> {code}
> /**
> The copy of the hive client that is used for execution. Currently this must
> always be
> Hive 13 as this is the version of Hive that is packaged with Spark SQL. This
> copy of the
> client is used for execution related tasks like registering temporary
> functions or ensuring
> that the ThreadLocal SessionState is correctly populated. This copy of Hive
> is not used
> for storing persistent metadata, and only point to a dummy metastore in a
> temporary directory. */
> {code}
> The executionHive assumed to be a standard meta store located in temporary
> directory as a derby db. But hive.metastore.rawstore.impl was not filtered
> out so any custom implementation of the metastore with other storage
> properties (not JDO) will persist that temporary functions.
> CassandraMetaStore from DataStax Enterprise is one of examples.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
