Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1535#issuecomment-50579659
Hey @nkronenfeld - I traced through the exact function call more closely
and I actually think it's fine. The issue I pointed out in the JIRA is
orthogonal. So I'm fine to just revert this back to always showing the status.
However, we should not mark this as a developer API. This is a stable API we
are happy to support forever.
Still, this will cause a significant amount of object allocation due to the
way other internal function calls happen (it is basically O(all blocks)) for an
application. It might be nice to add a note to the docs that the operation
might be expensive and should not be called inside of a critical code path.
Thought we could likely optimize those things down the road.
---
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.
---
