Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9982#issuecomment-160368342
@tdas, my idea behind adding a new state was to give better error messages
in the case where a stop gets interrupted and then the user calls
`getOrCreate()` and continues to use a streaming context which might not be in
a usable state; my concern was that this case would lead to hard-to-diagnose
errors, rather than easy-to-understand "this context is not in a usable state"
messages.
And yes, this relies on the methods called in `stop()` being idempotent;
there's an inline comment addressing that. AFAIK the current code is
idempotent, but it would be good to double-check this for each component.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
