GitHub user vanzin opened a pull request:
https://github.com/apache/spark/pull/7026
[SPARK-8066, SPARK-8067] [hive] Add support for Hive 1.0, 1.1 and 1.2.
Allow HiveContext to connect to metastores of those versions; some new shims
had to be added to account for changing internal APIs.
A new test was added to exercise the "reset()" path which now also requires
a shim; and the test code was changed to use a directory under the build's
target to store ivy dependencies. Without that, at least I consistently run
into issues with Ivy messing up (or being confused) by my existing caches.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vanzin/spark SPARK-8067
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/7026.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 #7026
----
commit 3e2e67b5d8277b9e52b8a1f2e0268fe2c4044540
Author: Marcelo Vanzin <[email protected]>
Date: 2015-06-25T19:25:18Z
[SPARK-8066, SPARK-8067] [hive] Add support for Hive 1.0, 1.1 and 1.2.
Allow HiveContext to connect to metastores of those versions; some new shims
had to be added to account for changing internal APIs.
A new test was added to exercise the "reset()" path which now also requires
a shim; and the test code was changed to use a directory under the build's
target to store ivy dependencies. Without that, at least I consistently run
into issues with Ivy messing up (or being confused) by my existing caches.
----
---
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]
