Radeity opened a new issue, #13970: URL: https://github.com/apache/dolphinscheduler/issues/13970
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement. ### Description Some tasks can be submitted in different way, like Spark on Yarn / Kubernetes, currently, we have abstracted `AbstractYarnTask` and made `SparkTask` inherit from it. This is not a good hierarchy, like we don't have to get applicationId in scenario of Spark on Kubernetes, also, logic of application cancelation is a bit messy. Can we restructure codes in a better way? ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
