Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2337#issuecomment-57572402
I've given it some thought and I don't think that we should merge the more
general async. mechanism that I described in #2482. It had some confusing
semantics surrounding cancellation (see the discussion of Thread.interrupt) and
was probably more general than what most users need.
Given that we should probably keep the current async APIs, this PR's change
looks good. I'm going to merge this into `master`. Thanks for this commit and
sorry for the long review delay!
---
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
