[
https://issues.apache.org/jira/browse/HADOOP-9192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548862#comment-13548862
]
Suresh Srinivas commented on HADOOP-9192:
-----------------------------------------
bq. and should be compatible for HDFS
So, it is okay if it is incompatible for YARN and MapReduce V2? In HADOOP-9151,
your veto was all about not introducing incompatible changes for 2.0.2-alpha
users and CDH users. However, in this jira, you are okay with the
incompatibility for YARN and MRV2, even though it affects 2.0.2-alpha users. Is
it because CDH4 sets the expectation about YARN and MRV2 to be alpha quality
and focus on MRv1 as GA option for mapreduce. This makes me think that when CDH
calls some thing as alpha it is okay to make incompatible changes and when
apache calls a release as alpha it is not okay to make incompatible changes?
This leads me to conclude that most of the HADOOP-9151 objections are only
motivated by CDH compatibility alone.
> Move token related request/response messages to common
> ------------------------------------------------------
>
> Key: HADOOP-9192
> URL: https://issues.apache.org/jira/browse/HADOOP-9192
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Affects Versions: 2.0.2-alpha
> Reporter: Suresh Srinivas
> Assignee: Suresh Srinivas
> Attachments: HADOOP-9192.patch, HADOOP-9192.patch, HADOOP-9192.patch
>
>
> Get, Renew and Cancel delegation token requests and responses are repeated in
> HDFS, Yarn and MR. This jira proposes to move these messages into
> Security.proto in common.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
