[ https://issues.apache.org/jira/browse/YARN-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhijie Shen resolved YARN-1835. ------------------------------- Resolution: Invalid The ApplicationHistoryManager has a new implementation, which doesn't have the aforementioned issue. > History client service needs to be more robust > ---------------------------------------------- > > Key: YARN-1835 > URL: https://issues.apache.org/jira/browse/YARN-1835 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Zhijie Shen > Assignee: Zhijie Shen > > While doing the test, I've found the following issues so far: > 1. The history file not found exception is exposed to the user directly, > which is better to be caught and translated into ApplicationNotFound. > 2. NPE will be exposed as well, since ApplicationHistoryManager doesn't do > necessary null check. > In addition, TestApplicationHistoryManagerImpl missed to test most > ApplicationHistoryManager methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)