Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/1723#issuecomment-53509499
Yeah, better to not modify Spark's default behavior. One solution for this
is to modify Utils.getCallSite to take a parameter - a filter function. There
will be the default filter function that is same as the SPARK_rEGEX check. That
will preserve the default functionality. But the streaming code will plugin its
own filter function, where it can do all the
SPARK_REGEX+STREAMING_REGEX+SCALA_REGEX check.
How does that sound?
Also, in the screen shot the only active stage is "<unknown>:0" , but
should be the file:line-number of the site where streamingContext.start() was
called. See the code in ReceiverTracker. Can you set the callsite correctly
over there, so that it does not show "<unknown>:0"
---
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
