Return-Path: 
 <user-return-17435-apmail-hadoop-user-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-user-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 0666E10247
	for <apmail-hadoop-user-archive@minotaur.apache.org>;
 Fri, 17 Oct 2014 00:16:00 +0000 (UTC)
Received: (qmail 79910 invoked by uid 500); 17 Oct 2014 00:15:55 -0000
Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org
Received: (qmail 79777 invoked by uid 500); 17 Oct 2014 00:15:55 -0000
Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hadoop.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hadoop.apache.org>
List-Post: <mailto:user@hadoop.apache.org>
List-Id: <user.hadoop.apache.org>
Reply-To: user@hadoop.apache.org
Delivered-To: mailing list user@hadoop.apache.org
Received: (qmail 79767 invoked by uid 99); 17 Oct 2014 00:15:54 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Oct 2014 00:15:54 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of manojsameltech@gmail.com
 designates 209.85.216.43 as permitted sender)
Received: from [209.85.216.43] (HELO mail-qa0-f43.google.com) (209.85.216.43)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Oct 2014 00:15:49 +0000
Received: by mail-qa0-f43.google.com with SMTP id s7so3184137qap.16
        for <user@hadoop.apache.org>; Thu, 16 Oct 2014 17:15:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=6S18KY5a2E0qjbIQYT0zRJpwaHGEmjFPpST/xgH5S5c=;
        b=dBQOCvWv6bqsQ8n5w4JVspmsT+qM7P4p1q5fMvtYGzvaowQ2fkVDCBQvS0LRBBVeU6
         9dAv/3qx7Nz5aeKtdzvblTBmLE39XDoKRHVBTsPJ8xZ2tKVbcNvXz9K03C5/Lan5OpCx
         plH3WGcAeJPYtdMcn1+j76XoFOkVbVFA+rzKiKSVya0zqk5OPpoPO1d6vfyAT8d+KnhH
         qesAsUKdqjTgCciwC5AGvSzoYnCSgPFni4GJC964kmIVqPmUpZNoHGwxVHvM9YQRNvCu
         sxcmRABLt60n7toFCpWL8NGC1kX5UtfOzHzpcmjypROU4eYq0L7MDoHB0eUVXFr3KNtK
         NU/g==
MIME-Version: 1.0
X-Received: by 10.229.24.137 with SMTP id v9mr7465810qcb.16.1413504928792;
 Thu, 16 Oct 2014 17:15:28 -0700 (PDT)
Received: by 10.96.205.168 with HTTP; Thu, 16 Oct 2014 17:15:28 -0700 (PDT)
Date: Thu, 16 Oct 2014 17:15:28 -0700
Message-ID: 
 <CAAqMD1gxoXX-MoXFJ3poSwJXOj6y41NYL+fapYLE-_AAx-gZnA@mail.gmail.com>
Subject: hadoop 2.4 using Protobuf - How does downgrade back to 2.3 works ?
From: Manoj Samel <manojsameltech@gmail.com>
To: user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=001a113351a42bd339050593431e
X-Virus-Checked: Checked by ClamAV on apache.org

--001a113351a42bd339050593431e
Content-Type: text/plain; charset=UTF-8

Hadoop 2.4.0 mentions that FSImage is stored using protobuf. So upgrade
from 2.3.0 to 2.4 would work since 2.4 can read old (2.3) binary format and
write the new 2.4 protobuf format.

After using 2.4, if there is a need to downgrade back to 2.3, how would
that work ?

Thanks,

--001a113351a42bd339050593431e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hadoop 2.4.0 mentions that FSImage is stored using protobu=
f. So upgrade from 2.3.0 to 2.4 would work since 2.4 can read old (2.3) bin=
ary format and write the new 2.4 protobuf format.<div><br></div><div>After =
using 2.4, if there is a need to downgrade back to 2.3, how would that work=
 ?</div><div><br></div><div>Thanks,</div></div>

--001a113351a42bd339050593431e--