Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type;
  b=nceePRF2s/j+gQE7PRRQMXIIZbVNOezbJFyqR2YewslblsDXrHOJQBBurE2+7LOrGGfODYBidBGzDoG5sNjkurcxwqCoJKg+dBnLiD7c5Sw8R47+w3BDhjECCrTzWf7pH+YtMpcPl/m7Ux5tnwiTxxu1LJ1jHCIpkvIa62PgXgA=;
References: 
 <CA+qbEUMmAGzJFViN6dsLu14aOynn5+2LNw3bP5dC1e-n6VnfWQ@mail.gmail.com>
 <1365135106.53512.YahooMailNeo@web125703.mail.ne1.yahoo.com>
 <1365292905.87684.YahooMailNeo@web125703.mail.ne1.yahoo.com>
Message-ID: <1365464049.66202.YahooMailNeo@web125705.mail.ne1.yahoo.com>
Date: Mon, 8 Apr 2013 16:34:09 -0700 (PDT)
From: Tsz Wo Sze <szetszwo@yahoo.com>
Reply-To: Tsz Wo Sze <szetszwo@yahoo.com>
Subject: Re: VOTE: HDFS-347 merge
To: "hdfs-dev@hadoop.apache.org" <hdfs-dev@hadoop.apache.org>
In-Reply-To: <1365292905.87684.YahooMailNeo@web125703.mail.ne1.yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="-268986479-848870714-1365464049=:66202"

---268986479-848870714-1365464049=:66202
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Colin,=0A=0AThanks for closing the previous VOTE.=A0 (We usually count t=
he numbers of +1's and -1's, and then state whether the vote passes.=A0 Hop=
e that you could include such information next time.)=0A=0A=0AI withdraw my=
 -1.=0A=0A=0ATsz-Wo=0A=0A=0A=0A=0A________________________________=0A From:=
 Tsz Wo Sze <szetszwo@yahoo.com>=0ATo: "hdfs-dev@hadoop.apache.org" <hdfs-d=
ev@hadoop.apache.org> =0ASent: Sunday, April 7, 2013 8:01 AM=0ASubject: Re:=
 VOTE: HDFS-347 merge=0A =0A=0AThe patch in HDFS-4661 has addressed the pro=
blem I raised.=A0 Once the previous VOTE has be concluded, I will remove my=
 -1.=A0 Thanks.=0A=0ATsz-Wo=0A=0A=0A=0A________________________________=0A =
From: Tsz Wo Sze <szetszwo@yahoo.com>=0ATo: "hdfs-dev@hadoop.apache.org" <h=
dfs-dev@hadoop.apache.org> =0ASent: Friday, April 5, 2013 12:11 PM=0ASubjec=
t: Re: VOTE: HDFS-347 merge=0A =0AColin,=0A=0AWe usually conclude the last =
VOTE before starting a new one.=A0 Otherwise, people may be confused betwee=
n the VOTEs.=A0 (In case you don't know our convention.=A0 Please check wit=
h someone before starting a VOTE.=A0 Thanks.)=0A=0A=0A-1=0A* The previous V=
OTE started by Colin has not been concluded.=0A=0A* The branch is not ready=
.=A0 The code misuses DataTransferProtocol.=A0 Documentation of the new con=
f properties are missing.=A0 Also, the code in the branch needs to be polis=
hed.=A0 See HDFS-347 and HDFS-4661 for more details.=0A=0ATsz-Wo=0A=0A=0A=
=0A________________________________=0AFrom: Colin McCabe <cmccabe@alumni.cm=
u.edu>=0ATo: hdfs-dev@hadoop.apache.org =0ASent: Tuesday, April 2, 2013 7:3=
2 AM=0ASubject: VOTE:=0A HDFS-347 merge=0A=0AHi all,=0A=0AI think it's time=
 to merge the HDFS-347 branch back to trunk.=A0 It's been under=0Areview an=
d testing for several months, and provides both a performance=0Aadvantage, =
and the ability to use short-circuit local reads without=0Acompromising sys=
tem security.=0A=0APreviously, we tried to merge this and the objection was=
 brought up that we=0Ashould keep the old, insecure short-circuit local rea=
ds around so that=0Aplatforms for which secure SCR had not yet been impleme=
nted could use it=0A(e.g. Windows).=A0 This has been addressed-- see HDFS-4=
538 for details.=0ASuresh has also volunteered to maintain the insecure SCR=
 code until secure=0ASCR can be implemented for Windows.=0A=0APlease cast y=
our vote by EOD Monday 4/8.=0A=0Abest,=0AColin
---268986479-848870714-1365464049=:66202--