Github user tejasapatil commented on the pull request:
https://github.com/apache/spark/pull/11723#issuecomment-200687233
@rxin : I would really like to have this PR in trunk. As things stand, for
anyone using their own scheduler, one has to maintain a patch over open source
release to have that glue in Spark. Re API breaking over Spark releases : I
agree that breaking APIs is bad. But it would be atleast better than the
current model of dealing with this: doing a merge for *every* release.
---
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
