You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Burak Yavuz (JIRA)" <ji...@apache.org> on 2016/09/13 19:58:20 UTC
[jira] [Updated] (SPARK-17531) Don't initialize Hive Listeners for
the Execution Client
[ https://issues.apache.org/jira/browse/SPARK-17531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Burak Yavuz updated SPARK-17531:
--------------------------------
Description:
If a user provides listeners inside the Hive Conf, the configuration for these listeners are passed to the Hive Execution Client as well. This may cause issues for two reasons:
1. The Execution Client will actually generate garbage
2. The listener class needs to be both in the Spark Classpath and Hive Classpath
The configuration can be overwritten within
{code}
HiveUtils.newTemporaryConfiguration
{code}
> Don't initialize Hive Listeners for the Execution Client
> --------------------------------------------------------
>
> Key: SPARK-17531
> URL: https://issues.apache.org/jira/browse/SPARK-17531
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 2.0.0
> Reporter: Burak Yavuz
>
> If a user provides listeners inside the Hive Conf, the configuration for these listeners are passed to the Hive Execution Client as well. This may cause issues for two reasons:
> 1. The Execution Client will actually generate garbage
> 2. The listener class needs to be both in the Spark Classpath and Hive Classpath
> The configuration can be overwritten within
> {code}
> HiveUtils.newTemporaryConfiguration
> {code}
--
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