[
https://issues.apache.org/jira/browse/SPARK-5846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kay Ousterhout updated SPARK-5846:
--
Description:
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.
was: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). This should be done before
the job is run.
Spark SQL should set job description and pool *before* running jobs
---
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
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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
