You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Cheng Lian (JIRA)" <ji...@apache.org> on 2015/02/19 02:53:11 UTC
[jira] [Resolved] (SPARK-5846) Spark SQL does not correctly set job
description and scheduler pool
[ https://issues.apache.org/jira/browse/SPARK-5846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cheng Lian resolved SPARK-5846.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.3.0
Issue resolved by pull request 4630
[https://github.com/apache/spark/pull/4630]
> Spark SQL does not correctly set job description and scheduler pool
> -------------------------------------------------------------------
>
> Key: SPARK-5846
> URL: https://issues.apache.org/jira/browse/SPARK-5846
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 1.3.0, 1.2.1
> Reporter: Kay Ousterhout
> Assignee: Kay Ousterhout
> Priority: Critical
> Fix For: 1.3.0
>
>
> Spark SQL current sets the scheduler pool and job description AFTER jobs run (see https://github.com/apache/spark/blob/master/sql/hive-thriftserver/v0.13.1/src/main/scala/org/apache/spark/sql/hive/thriftserver/Shim13.scala#L168 -- which happens after calling hiveContext.sql). As a result, the description for a SQL job ends up being the SQL query corresponding to the previous job. This should be done before the job is run so the description is correct.
--
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