You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2015/08/21 22:59:46 UTC
[jira] [Assigned] (SPARK-10121) Custom Class added through Spark
SQL's add jar command may not be in the class loader used by metadataHive
[ https://issues.apache.org/jira/browse/SPARK-10121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Apache Spark reassigned SPARK-10121:
------------------------------------
Assignee: Apache Spark
> Custom Class added through Spark SQL's add jar command may not be in the class loader used by metadataHive
> ----------------------------------------------------------------------------------------------------------
>
> Key: SPARK-10121
> URL: https://issues.apache.org/jira/browse/SPARK-10121
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 1.4.0
> Reporter: Yin Huai
> Assignee: Apache Spark
> Priority: Critical
>
> One symptom is that people connecting to Spark SQL through thrift server may see class not found exception when accessing their tables using custom serdes.
> I feel https://github.com/apache/spark/blob/master/sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/commands.scala#L103 is not enough. We probably should set the class loader explicitly to metadataHive like what we do at https://github.com/apache/spark/blob/master/sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/commands.scala#L101.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org