Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/21923
the only other cases I have heard people ask for this are hopefully covered
by the new barrier scheduling.
While I agree that we need to be careful about creating APIs to properly
think about them, I don't think we should block a useful feature on having more
than one use case. We just need to make sure its mark properly until we are
comfortable with it. This is marked as DeveloperApi which should cover that.
Currently this isn't putting any user docs up which might make sense if our
use case is debugging and we want to try to vet this as an alpha api. thoughts?
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
