You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Eric Yang (JIRA)" <ji...@apache.org> on 2017/09/19 18:58:00 UTC
[jira] [Created] (YARN-7216) Missing ability to list configuration
vs status
Eric Yang created YARN-7216:
-------------------------------
Summary: Missing ability to list configuration vs status
Key: YARN-7216
URL: https://issues.apache.org/jira/browse/YARN-7216
Project: Hadoop YARN
Issue Type: Bug
Components: api, applications
Reporter: Eric Yang
Assignee: Eric Yang
API Server has /ws/v1/services/{service_name}. This REST end point returns Services object which contains both configuration and status. When status or macro based parameters changed in Services object, it can confuse UI code to making configuration changes. The suggestion is to preserve a copy of configuration object independent of status object. This gives UI ability to change services configuration and update configuration.
Similar to Ambari, it might provide better information if we have the following separated REST end points:
{code}
/ws/v1/services/{service_name}/config
/ws/v1/services/{service_name}/status
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org