[
https://issues.apache.org/jira/browse/YARN-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhijie Shen updated YARN-1744:
------------------------------
Description: When we started with the feature, the module only contains the
source code of generic application history service, therefore, it was named
applicationhistoryservice. However, as time goes on, we have been moving on
with per framework historic data (see YARN-1530). The code base of this module
has already gone beyond generic application history service, and include
timeline service as well. It's good to come up a more accurate name to describe
the project asap to prevent people from being confused by the module name about
what service it can provide. Probably we need to refactor the AHS related
classes as well for clarity. (was: As the module is containing the stuff more
than application history service, it's better for us come up a better name for
it, do necessary refactoring asap.)
> Renaming applicationhistoryservice module
> -----------------------------------------
>
> Key: YARN-1744
> URL: https://issues.apache.org/jira/browse/YARN-1744
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Zhijie Shen
> Assignee: Zhijie Shen
>
> When we started with the feature, the module only contains the source code of
> generic application history service, therefore, it was named
> applicationhistoryservice. However, as time goes on, we have been moving on
> with per framework historic data (see YARN-1530). The code base of this
> module has already gone beyond generic application history service, and
> include timeline service as well. It's good to come up a more accurate name
> to describe the project asap to prevent people from being confused by the
> module name about what service it can provide. Probably we need to refactor
> the AHS related classes as well for clarity.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
