Github user klion26 commented on the issue:
https://github.com/apache/spark/pull/19145
@squito I agree with you that this should be handled by yarn.
In my opinion, this is some form of defensive programming. The Spark
Streaming and structured streaming will both request more resource than they
want, if these things happen.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
