[
https://issues.apache.org/jira/browse/HDFS-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018615#comment-13018615
]
Tsz Wo (Nicholas), SZE commented on HDFS-1822:
----------------------------------------------
> The alternative, as previously mentioned, was to patch the branch of any
> upcoming Apache Hadoop release with the bad opcode to match trunk.
Allen, thanks for providing the solution. What are the drawbacks for
committing Suresh's patch? Why can't we do both, i.e. fixing the bad opcode in
0.20-security and committing Suresh's patch?
> 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
