[
https://issues.apache.org/jira/browse/YARN-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14281089#comment-14281089
]
Sangjin Lee commented on YARN-3030:
-----------------------------------
OK, the regular pre-commit jenkins build is based on the trunk so my
incremental patch is not going to work with the regular pre-commit jenkins
build.
Then, I don't think we should generate cumulative patches (diff from the trunk)
as those would be impossible to review.
Should we create our own jenkins job? How does this process work with branch
development?
> set up ATS writer with basic request serving structure and lifecycle
> --------------------------------------------------------------------
>
> Key: YARN-3030
> URL: https://issues.apache.org/jira/browse/YARN-3030
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Sangjin Lee
> Assignee: Sangjin Lee
> Attachments: YARN-3030.001.patch
>
>
> Per design in YARN-2928, create an ATS writer as a service, and implement the
> basic service structure including the lifecycle management.
> Also, as part of this JIRA, we should come up with the ATS client API for
> sending requests to this ATS writer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
