Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/1723#issuecomment-52444695
This looks pretty promising!! However why do every DStream need to change?
The DStream parent class can do the following. Before calling compute(), it can
store the previous callsite, and set the new callsite, and then call compute.
Upon returning from compute(), it can reset the previous callsite. As far as I
can see, that should work for all the DStreams without modifying every single
stream.
Also can you show us a new screenshot of what it looks like now. Does it
look the same as the on posted in this PR?
---
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
