Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10991#issuecomment-193397498
The Master REST API functionality which existed prior to the unification
with the Spark driver REST API should still work after this change, so we
shouldn't break or remove those methods.
I think that there are a few ways to handle this JIRA / task, some more
complex than others. The only "must have" requirement for 2.0 is removing the
HistoryServer functionality; other cleanup and interface refactoring can be
deferred for later. So, I wouldn't try to do any major refactoring or cleanup;
just remove the feature so we get the API / functionality change in and address
the other pieces later.
---
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]
