Hitesh Shah commented on YARN-2375:

bq. Do you mean the semantic incompatible?

Semantic or not - it looks to be an incompatible change as you are expecting 
applications to change to be able to use Timeline "correctly".

bq. It sounds reasonable. Does it break any depending project?

Yes it does break things. You are now expecting all downstream projects to 
change in terms of how to use the TimelineClient and the fact that they also 
now need to inspect the value of a YARN config property. Changing 
distributed-shell should have been a red-flag from a compatibility point of 

Agreed that the change is reasonable but you cannot make changes like these in 
a patch release. 

> Allow enabling/disabling timeline server per framework
> ------------------------------------------------------
>                 Key: YARN-2375
>                 URL: https://issues.apache.org/jira/browse/YARN-2375
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Jonathan Eagles
>            Assignee: Mit Desai
>             Fix For: 2.7.0, 2.6.1
>         Attachments: YARN-2375.1.patch, YARN-2375.patch, YARN-2375.patch, 
> YARN-2375.patch, YARN-2375.patch
> This JIRA is to remove the ats enabled flag check within the 
> TimelineClientImpl. Example where this fails is below.
> While running secure timeline server with ats flag set to disabled on 
> resource manager, Timeline delegation token renewer throws an NPE. 

This message was sent by Atlassian JIRA

Reply via email to