GitHub user artem-aliev opened a pull request:

    https://github.com/apache/spark/pull/9178

    [SPARK-11208] [SQL] Filter out 'hive.metastore.rawstore.impl' from ex…

    …ecutionHive temporary config
    
    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. CassandraHiveMetaStore from 
DataStax Enterprise is one of examples.
    
    @marmbrus, @WangTaoTheTonic,  please review this trivial fix.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/artem-aliev/spark SPARK-11208

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/9178.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #9178
    
----
commit 563f2aafb148291a077d9d25797256fd6e4567af
Author: Artem Aliev <[email protected]>
Date:   2015-10-20T10:27:41Z

    [SPARK-11208] [SQL] Filter out 'hive.metastore.rawstore.impl' from 
executionHive temporary config
    
    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.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to