GitHub user vanzin opened a pull request:

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

    [SPARK-19084][sql] Ensure context class loader is set when initializing 
Hive.

    A change in Hive 2.2 (most probably HIVE-13149) causes this code path to 
fail,
    since the call to "state.getConf.setClassLoader" does not actually change 
the
    context's class loader. Spark doesn't yet officially support Hive 2.2, but 
some
    distribution-specific metastore client libraries may have that change (as 
certain
    versions of CDH already do), and this also makes it easier to support 2.2 
when it
    comes out.
    
    Tested with existing unit tests; we've also used this patch extensively 
with Hive
    metastore client jars containing the offending patch.


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

    $ git pull https://github.com/vanzin/spark SPARK-19804

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

    https://github.com/apache/spark/pull/17154.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 #17154
    
----
commit 324619620fff32b766068a0ea0f04aef67b2780e
Author: Marcelo Vanzin <[email protected]>
Date:   2017-03-03T19:27:41Z

    [SPARK-19084][sql] Ensure context class loader is set when initializing 
Hive.
    
    A change in Hive 2.2 (most probably HIVE-13149) causes this code path to 
fail,
    since the call to "state.getConf.setClassLoader" does not actually change 
the
    context's class loader. Spark doesn't yet officially support Hive 2.2, but 
some
    distribution-specific metastore client libraries may have that change (as 
certain
    versions of CDH already do), and this also makes it easier to support 2.2 
when it
    comes out.
    
    Tested with existing unit tests; we've also used this patch extensively 
with Hive
    metastore client jars containing the offending patch.

----


---
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