[
https://issues.apache.org/jira/browse/YARN-10244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214050#comment-17214050
]
Eric Badger commented on YARN-10244:
------------------------------------
I'm pretty confused with all of the JIRAs on this. In the future, I think we
should revert the JIRA using the JIRA that was committed. Let me summarize what
I think happened and you all can let me know if I have it right.
YARN-4946 committed to 3.2, so it is in 3.2, 3.3, and trunk
YARN-9848 reverted YARN-4946 from 3.3, so YARN-4946 only remains in 3.2
YARN-10244 reverted YARN-4946 from 3.2, so YARN-4946 has been completely
reverted
It's really confusing to me because YARN-4946 has the Fix Version set as 3.2.
And then this JIRA says it is backporting YARN-9848, instead of saying it's
reverting YARN-4946. Anyway, like I said above, if we're going to revert stuff,
I think it is better to do it on the JIRA where it was committed so that we
have a clear linear log of where it was committed to and reverted from. We can
also then look at the Fix Version for that particular JIRA and know where it is
actually committed
> backport YARN-9848 to branch-3.2
> --------------------------------
>
> Key: YARN-10244
> URL: https://issues.apache.org/jira/browse/YARN-10244
> Project: Hadoop YARN
> Issue Type: Bug
> Components: log-aggregation, resourcemanager
> Reporter: Steven Rand
> Assignee: Steven Rand
> Priority: Major
> Attachments: YARN-10244-branch-3.2.001.patch,
> YARN-10244-branch-3.2.002.patch, YARN-10244-branch-3.2.003.patch
>
>
> Backporting YARN-9848 to branch-3.2.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
