Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/16936
I agreed with @srowen. Streaming should not need to know the details about
the mode, and when someone changes other modules, they won't know these codes
inside streaming. I would like to see a cleaner solution.
In addition, when there are not enough resources in a cluster, even if the
user sets a large core number, they will still not be able to run the streaming
job. Hence, they should always be aware of this limitation of Streaming
receivers, and it seems not worth to fix this issue.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
