GitHub user yhuai opened a pull request:
https://github.com/apache/spark/pull/10204
[SQL] Try to run execution hive's derby in memory.
This PR tries to make execution hive's derby run in memory since it is a
fake metastore and every time we create a HiveContext, we will switch to a new
one. It is possible that it can reduce the flakyness of our tests that need to
create HiveContext (e.g. HiveSparkSubmitSuite). I will test it more. If it is a
valid improvement, I will create a jira.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yhuai/spark derbyInMemory
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/10204.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 #10204
----
commit 207895b798a5ff030fbdb8a9413b6b0e8d774c9f
Author: Yin Huai <[email protected]>
Date: 2015-12-08T18:21:14Z
Try to run execution hive's derby in memory.
----
---
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]
