[
https://issues.apache.org/jira/browse/YARN-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15014637#comment-15014637
]
Vinod Kumar Vavilapalli commented on YARN-3623:
-----------------------------------------------
[~xgong] / [~Naganarasimha] / [~sjlee0] / [~gtCarrera9], there are too many
JIRAs about this versioning topic and the discussion is split all over.
Let me try to consolidate the tickets. Let's use this one as the base JIRA for
introducing versioning. [~xgong], can you post part of your patch at YARN-4234
here?
I'll move this to be a common JIRA across v1, v2 and v1.5 and make all the
other JIRAs depend on this.
> Having the config to indicate the timeline service version
> ----------------------------------------------------------
>
> Key: YARN-3623
> URL: https://issues.apache.org/jira/browse/YARN-3623
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Zhijie Shen
> Assignee: Naganarasimha G R
>
> So far RM, MR AM, DA AM added/changed new config to enable the feature to
> write the timeline data to v2 server. It's good to have a YARN
> timeline-service.version config like timeline-service.enable to indicate the
> version of the running timeline service with the given YARN cluster. It's
> beneficial for users to more smoothly move from v1 to v2, as they don't need
> to change the existing config, but switch this config from v1 to v2. And each
> framework doesn't need to have their own v1/v2 config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
