[
https://issues.apache.org/jira/browse/YARN-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14328059#comment-14328059
]
Sangjin Lee commented on YARN-3040:
-----------------------------------
[~Naganarasimha], the scope of this JIRA is to provide a way for a YARN client
to set and pass information about the flow along with the application. With
this, we don't need to worry about actually creating a flow on the timeline
service side of things yet.
Basically we need the ability to set flow id, flow version, and the flow run id
as strings.
As for the cluster, I think trivially the cluster will be assumed to be the
same cluster it is on, so the client doesn't need to set it. The RM and/or the
aggregator will use the current cluster and write it out to the timeline
service storage.
> [Data Model] Implement client-side API for handling flows
> ---------------------------------------------------------
>
> Key: YARN-3040
> URL: https://issues.apache.org/jira/browse/YARN-3040
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Sangjin Lee
> Assignee: Robert Kanter
>
> Per design in YARN-2928, implement client-side API for handling *flows*.
> Frameworks should be able to define and pass in all attributes of flows and
> flow runs to YARN, and they should be passed into ATS writers.
> YARN tags were discussed as a way to handle this piece of information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
