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 "Zhijie Shen (JIRA)" <ji...@apache.org> on 2014/07/17 04:44:04 UTC

[jira] [Created] (YARN-2302) Refactor TimelineWebServices

Zhijie Shen created YARN-2302:
---------------------------------

             Summary: Refactor TimelineWebServices
                 Key: YARN-2302
                 URL: https://issues.apache.org/jira/browse/YARN-2302
             Project: Hadoop YARN
          Issue Type: Sub-task
          Components: timelineserver
            Reporter: Zhijie Shen
            Assignee: Zhijie Shen


Now TimelineWebServices contains non-trivial logic to process the HTTP requests, manipulate the data, check the access, and interact with the timeline store.

I propose the move the data-oriented logic to a middle layer (so called TimelineDataManager), and TimelineWebServices only processes the requests, and call TimelineDataManager to complete the remaining tasks.

By doing this, we make the generic history module reuse TimelineDataManager internally (YARN-2033), invoking the putting/getting methods directly. Otherwise, we have to send the HTTP requests to TimelineWebServices to query the generic history data, which is not an efficient way.



--
This message was sent by Atlassian JIRA
(v6.2#6252)