Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/8998#issuecomment-146033999
Checking which types of dstreams are used and what configurations are used
and accordingly throwing errors seems to be complicated and brittle. I think
its best to throw a warning.
In general, if they are not using WAL or reliable sources, they should be
aware that they are going to loose data under failures anyways, and they should
be aware of that anyways. Dynamic allocation really does not aggravate the
problem significantly more.
---
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
