[
https://issues.apache.org/jira/browse/SPARK-42472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18072359#comment-18072359
]
Shekhar Prasad Rajak commented on SPARK-42472:
----------------------------------------------
```proto
SetJobGroupCommand set_job_group = 20;
ClearJobGroupCommand clear_job_group = 21;
CancelJobGroupCommand cancel_job_group = 22;
```
and message definitions:
```proto
message SetJobGroupCommand {
string group_id = 1;
string description = 2;
bool interrupt_on_cancel = 3;
}
message ClearJobGroupCommand {}
message CancelJobGroupCommand {
string group_id = 1;
}
```
and should we leverage : SparkContext.setJobGroup / cancelJobGroup /
clearJobGroup APIs ?
> Make spark connect supporting canceling job group
> -------------------------------------------------
>
> Key: SPARK-42472
> URL: https://issues.apache.org/jira/browse/SPARK-42472
> Project: Spark
> Issue Type: Sub-task
> Components: Connect, ML
> Affects Versions: 3.4.0
> Reporter: Ruifeng Zheng
> Priority: Major
>
> PySpark ML crossValidator relies on this:
> proposal:
> when spark client sending request, can we make it send with a "job_group_id",
> and in server side, for each request that with the same (user_id,
> job_group_id), handling request in a fixed thread
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
