Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 12 Apr 2011 00:10:05 +0000 (UTC)
From: "Tsz Wo (Nicholas), SZE (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <600374634.51154.1302567005833.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1154777554.44805.1302292745765.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-1822) Editlog opcodes overlap between 20
 security and later releases
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Hey Allen, we are talking about Apache Hadoop trunk and Apache Hadoop 0.20-security. Fred's Bargain Basement Distribution of Apache Hadoop is out of our picture.

For your question:
- Suppose it is neither an incompatible change nor introducing other bad behaviors.  Suppose also the original patch was submitted to Apache Hadoop.  We should accept it.
- On the other hand, if a patch is fixing a private distribution, we should not accept it.

> 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