[ https://issues.apache.org/jira/browse/YARN-5184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15652388#comment-15652388 ]
Sangjin Lee commented on YARN-5184: ----------------------------------- Hmm, I definitely understand the desire to minimize incompatibilities even for major versions. On the other hand, it might not be best if we say zero incompatibilities even for a major version upgrade. That would severely limit the ability to make more substantial changes to deliver useful features and get rid of tech debt, and so on. I think you would agree that there needs to be a happy medium here. I don't have a strong opinion on this specific one for 3.0. If you feel strongly that this would be a major issue for 3.0, I'd be happy to keep the default methods. Do let me know, and I will update the patches and this JIRA. Thanks! > Fix up incompatible changes introduced on ContainerStatus and NodeReport > ------------------------------------------------------------------------ > > Key: YARN-5184 > URL: https://issues.apache.org/jira/browse/YARN-5184 > Project: Hadoop YARN > Issue Type: Bug > Components: api > Affects Versions: 2.8.0, 2.9.0 > Reporter: Karthik Kambatla > Assignee: Sangjin Lee > Priority: Blocker > Attachments: YARN-5184-branch-2.8.poc.patch, > YARN-5184-branch-2.poc.patch > > > YARN-2882 and YARN-5430 broke compatibility by adding abstract methods to > ContainerStatus. Since ContainerStatus is a Public-Stable class, adding > abstract methods to this class breaks any extensions. > To fix this, we should add default implementations to these new methods and > not leave them as abstract. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org