Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/1291#issuecomment-48407479
Actually, I think its worse if this is done for StateDStream, as in
StateDStream the computation should be run even if there is no input data, as
it is expected that the state update function is called on all the (key, state)
pairs even if there is no new data.
Regarding the fundamental reason behind doing this change, it seems that it
is a nice-to-have from the UI point of view, and not really a system
optimization. Regarding that, I dont have a strong reasoning against this but I
have found that it is more confusing to have no jobs show up in the UI, as it
is not even clear whether anything is running at all.
---
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.
---
