[YARN-1744] Renaming applicationhistoryservice module

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Assignee: Zhijie Shen
• Reporter: Zhijie Shen
• Created: 21/Feb/14 04:49
• Updated: 01/May/15 22:03
• Resolved: 01/May/15 22:03

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.

Issue Links

• relates to: YARN-1530 [Umbrella] Store, manage and serve per-framework application-timeline data