Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/4216#issuecomment-72289589
@pwendell @mateiz I realize I'm chiming in late here, but I think the
primary concern is that the protocol doesn't satisfy the principle of least
astonishment with respect to what people expect from HTTP submission gateways.
Eventually, whether in Spark itself or in some future project built on top,
there will probably end up being a standard way of submitting Spark
applications through a REST interface. If there's a remote chance that this
protocol might become that in the future, I think it's worthwhile thinking more
critically about it and why we're deviating from more standard REST practices.
For example, I don't think Dale's concerns on the JIRA were really addressed in
a rigorous way. If, on the other hand, the idea is that Spark would only ever
use this internally, my personal take is that there's no issue with getting it
in for 1.3.
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
