[
https://issues.apache.org/jira/browse/HDFS-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018600#comment-13018600
]
Suresh Srinivas commented on HDFS-1822:
---------------------------------------
There are releases using this in production. These releases are not off of
Apache. We are making explicit effort to make Apache the place for hadoop
releases. In this transition, unfortunately users have deployed other
distributions. The *cost of fixing this is small*, the patch is really not
significant and it provides upgrade path for users to move to official Apache
Hadoop releases.
I understand that this is not a problem for LinkedIn. But it is for other
folks. If you were in that boat, not sure how you would have voted on this
issue.
In this kind of voting, I think the community suffers. I accept the -1 and
withdraw my changes.
> Editlog opcodes overlap between 20 security and later releases
> --------------------------------------------------------------
>
> Key: HDFS-1822
> URL: https://issues.apache.org/jira/browse/HDFS-1822
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.21.0, 0.22.0, 0.23.0
> Reporter: Suresh Srinivas
> Assignee: Suresh Srinivas
> Priority: Blocker
> Fix For: 0.22.0, 0.23.0
>
> Attachments: HDFS-1822.patch
>
>
> Same opcode are used for different operations between 0.20.security, 0.22 and
> 0.23. This results in failure to load editlogs on later release, especially
> during upgrades.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
