[
https://issues.apache.org/jira/browse/YARN-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhijie Shen updated YARN-1407:
--
Description:
RMAppState isn't a public facing enum like YarnApplicationState, so we
shouldn't return values or list filters that come from it. However, some Blocks
and AppInfo are still using RMAppState.
It is not 100% clear to me whether or not fixing this would be a
backwards-incompatible change. The change would only reduce the set of
possible strings that the API returns, so I think not. We have also been
changing the contents of RMAppState since 2.2.0, e.g. in YARN-891. It would
still be good to fix this ASAP (i.e. for 2.2.1).
was:
RMAppState isn't a public facing enum like YarnApplicationState, so we
shouldn't return values that come from it.
It is not 100% clear to me whether or not fixing this would be a
backwards-incompatible change. The change would only reduce the set of
possible strings that the API returns, so I think not. We have also been
changing the contents of RMAppState since 2.2.0, e.g. in YARN-891. It would
still be good to fix this ASAP (i.e. for 2.2.1).
Summary: RM Web UI and REST APIs should uniformly use
YarnApplicationState (was: apps REST API filters queries by
YarnApplicationState, but includes RMAppStates in response)
RM Web UI and REST APIs should uniformly use YarnApplicationState
-
Key: YARN-1407
URL: https://issues.apache.org/jira/browse/YARN-1407
Project: Hadoop YARN
Issue Type: Bug
Affects Versions: 2.2.0
Reporter: Sandy Ryza
Assignee: Sandy Ryza
Attachments: YARN-1407-1.patch, YARN-1407.patch
RMAppState isn't a public facing enum like YarnApplicationState, so we
shouldn't return values or list filters that come from it. However, some
Blocks and AppInfo are still using RMAppState.
It is not 100% clear to me whether or not fixing this would be a
backwards-incompatible change. The change would only reduce the set of
possible strings that the API returns, so I think not. We have also been
changing the contents of RMAppState since 2.2.0, e.g. in YARN-891. It would
still be good to fix this ASAP (i.e. for 2.2.1).
--
This message was sent by Atlassian JIRA
(v6.1#6144)
