You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Gengliang Wang (Jira)" <ji...@apache.org> on 2023/07/29 20:46:00 UTC
[jira] [Resolved] (SPARK-44591) Add jobTags to SparkListenerSQLExecutionStart
[ https://issues.apache.org/jira/browse/SPARK-44591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gengliang Wang resolved SPARK-44591.
------------------------------------
Fix Version/s: 3.5.0
Resolution: Fixed
Issue resolved by pull request 42216
[https://github.com/apache/spark/pull/42216]
> Add jobTags to SparkListenerSQLExecutionStart
> ---------------------------------------------
>
> Key: SPARK-44591
> URL: https://issues.apache.org/jira/browse/SPARK-44591
> Project: Spark
> Issue Type: Bug
> Components: Connect
> Affects Versions: 3.5.0, 4.0.0
> Reporter: Jean-Francois Desjeans Gauthier
> Assignee: Jean-Francois Desjeans Gauthier
> Priority: Major
> Fix For: 3.5.0
>
>
> As part SPARK-43952, users can define job tags via SparkContext.addJobTag. These tags are then used to trigger cancelation via SparkContext.cancelJobsByTag. Furthermore, these tags can be used to logically group multiple jobs together.
> Listener of job events can retrieve job tags via SparkListenerJobStart.props.getProperty(SparkContext.SPARK_JOB_TAGS)
> Listener of SQL events can link SparkListenerJobStart & SparkListenerSQLExecutionStart via SparkListenerJobStart.props.getProperty(SQLExecution.EXECUTION_ID_KEY).
> However, some SQL executions do not trigger jobs (i.e. commands). As such listeners of SQL executions cannot resolve job tags of all executions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org