[
https://issues.apache.org/jira/browse/YARN-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280546#comment-14280546
]
Sangjin Lee commented on YARN-2928:
-----------------------------------
As far as I can tell, all server code has the naming
{{org.apache.hadoop.yarn.server.[feature_name\]}}. Wouldn't it be good to stick
with that then? How about the following then?
{noformat}
common: org.apache.hadoop.yarn.timelineservice.*
client: org.apache.hadoop.yarn.client.api.timelineservice.*
server: org.apache.hadoop.yarn.server.timelineservice.*
{noformat}
One thing is the current ATS code in yarn-api is in
{{org.apache.hadoop.yarn.client.api.records.timeline}} so it may become a
source of confusion as the new name sounds very similar. We'll just need to
find a way to differentiate them (via plenty of documentation or renaming
things).
> Application Timeline Server (ATS) next gen: phase 1
> ---------------------------------------------------
>
> Key: YARN-2928
> URL: https://issues.apache.org/jira/browse/YARN-2928
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: timelineserver
> Reporter: Sangjin Lee
> Assignee: Vinod Kumar Vavilapalli
> Priority: Critical
> Attachments: ATSv2.rev1.pdf, ATSv2.rev2.pdf
>
>
> We have the application timeline server implemented in yarn per YARN-1530 and
> YARN-321. Although it is a great feature, we have recognized several critical
> issues and features that need to be addressed.
> This JIRA proposes the design and implementation changes to address those.
> This is phase 1 of this effort.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
