[
https://issues.apache.org/jira/browse/YARN-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064528#comment-14064528
]
Hadoop QA commented on YARN-2302:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12656211/YARN-2302.1.patch
against trunk revision .
{color:red}-1 patch{color}. Trunk compilation may be broken.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4336//console
This message is automatically generated.
> 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
> Attachments: YARN-2302.1.patch
>
>
> 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)
