hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-1822) Editlog opcodes overlap between 20 security and later releases
Date Tue, 12 Apr 2011 01:27:06 GMT

    [ https://issues.apache.org/jira/browse/HDFS-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018664#comment-13018664

Tsz Wo (Nicholas), SZE commented on HDFS-1822:

> Show me where the tarball ...

Why a tarball suddenly becomes so important?  I am surprised.  Do you count 0.22 or 0.23?
 The tarballs are not out there yet.

Once a release is out, we are not allow to make incompatible changes but changing opcodes
is fine as long as the layout version is updated and it is backward compatible.  As mentioned
earlier, opcode is not necessarily unique across different layout versions.

> But here's the problem: this patch and my example cover both of these cases. ...

I intended to make two cases mutually exclusive.  The second case should be: "if a patch is
only fixing a private distribution but not Apache Hadoop trunk/branches".  Sorry that I did
not make it clear.

> ... Could someone generate a JIRA list that tracks the changes in the opcodes? ...

It can be done by "svn log".

> 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

View raw message