mridulm commented on PR #56055: URL: https://github.com/apache/spark/pull/56055#issuecomment-4671953037
As I said before, I would suggest working towards integrating into `DAGScheduler` with a principled solution; rather than trying to introduce extension mechanisms just to derisk the work : this is a feasible approach for a prototype, but I believe it has graduated from there (I saw PR's which dropped `Experimental` from the interfaces as well) If we want to make `DAGScheduler` pluggable - that could be a design in itself - and should be approached as such. To be honest, there is a case to be made for that given the complexity. I am -1 on this specific direction for the change until then. +CC @jiangxb1987 as you reviewed and approved this PR as well. -- 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]
