summaryzb commented on PR #50814:
URL: https://github.com/apache/spark/pull/50814#issuecomment-2931023578
Fine, update the PR description.
```
1. Cancel shuffle queryStage only When it's not reused nor reusing others
2. Mark the cancellable queryStage when it's not completed yet in
reOptimize stage
3. When cancellable queryStage is determined to be cancelled by
costEvaluator(cancellable queryStage in `EmptyPropagate` should always be
cancelled), the queryStage has no relation with current logical plan nor
physical plan any more
4. Cancel the queryStage after the corresponding job is completed, will
effect nothing
5. Cancel the queryStage when the corresponding job is running, the job
will be cancelled
6. Cancel the queryStage before he corresponding job is started, the job
will still be submitted, this case should be optimized in future commit,
however it's not worse than before this pr
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
