Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CA+RK=_DFYz=wL1ykKf+69FBn6U9QdVWcnDjqU7m7gHNR66yO6A@mail.gmail.com>
References: 
 <CA+RK=_DFYz=wL1ykKf+69FBn6U9QdVWcnDjqU7m7gHNR66yO6A@mail.gmail.com>
From: Jean-Marc Spaggiari <jean-marc@spaggiari.org>
Date: Thu, 16 Oct 2014 09:55:02 -0400
Message-ID: 
 <CAPQV63X+BUr+MRyxXB2=1u-25Sy340Vy07UEf8YmE_bY_ouS3A@mail.gmail.com>
Subject: Re: The 2nd HBase 0.98.7 release candidate (RC1) is available, vote
 closing 10/15/2014
To: dev <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary=001a11c1f0227c76a805058a99d4

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

Sorry, this was stuck in my draft folder... Did not get a chance to run the
perf but will do that after Strata.

Downloaded, verified signature for both hadoop1 and hadoop2, uncompressed
=3D> All passed.
Checked RAT on sources =3D> Passed.
Checked content =3D> CHANGES.txt date is strange. "Release 0.98.7 -
10/13/2014" Is not the packaging date nor the potential release date. Not a
blocker.
Checked content =3D> README.txt links are not correct. 404.
Started standalone, checked UI =3D> Passed
Checked logs =3D> I got the 2 lines below. Seems that we clear or read
something twice and I think it should have been done only once... Not 100%
sure.
2014-10-09 10:41:46,494 DEBUG [main-EventThread] hbase.ZKNamespaceManager:
Updating namespace cache from node default with data: \x0A\x07default
2014-10-09 10:41:46,504 DEBUG [main-EventThread] hbase.ZKNamespaceManager:
Updating namespace cache from node default with data: \x0A\x07default
HBCK, create (150 regions), put, scan, get, flush, major_compact =3D> Passe=
d,
but should major_compact flush first(*)


(*) Same as reported before, should the 2nd scan below be reporting only a
single row? Like, should major_compaction trigger a flush first?
hbase(main):019:0> scan 't1', {RAW =3D> true, VERSIONS =3D> 10}
ROW
COLUMN+CELL

 row1                                         column=3Df1:c1,
timestamp=3D1412866068992,
value=3DTheValue1

 row1                                         column=3Df1:c1,
timestamp=3D1412866068974,
value=3DTheValue1

 row1                                         column=3Df1:c1,
timestamp=3D1412866068945,
value=3DTheValue1

 row1                                         column=3Df1:c1,
timestamp=3D1412866068931,
value=3DTheValue1

 row1                                         column=3Df1:c1,
timestamp=3D1412866068919,
value=3DTheValue1

 row1                                         column=3Df1:c1,
timestamp=3D1412866068894,
value=3DTheValue1

 row1                                         column=3Df1:c1,
timestamp=3D1412866068877,
value=3DTheValue1

 row1                                         column=3Df1:c1,
timestamp=3D1412866068863,
value=3DTheValue1

 row1                                         column=3Df1:c1,
timestamp=3D1412866068849,
value=3DTheValue1

 row1                                         column=3Df1:c1,
timestamp=3D1412866068834,
value=3DTheValue1

1 row(s) in 0.4530 seconds

hbase(main):020:0> major_compact 't1'
0 row(s) in 0.1920 seconds

hbase(main):021:0> scan 't1', {RAW =3D> true, VERSIONS =3D> 10}
ROW
COLUMN+CELL

 row1                                         column=3Df1:c1,
timestamp=3D1412866068992,
value=3DTheValue1

 row1                                         column=3Df1:c1,
timestamp=3D1412866068974,
value=3DTheValue1

 row1                                         column=3Df1:c1,
timestamp=3D1412866068945,
value=3DTheValue1

 row1                                         column=3Df1:c1,
timestamp=3D1412866068931,
value=3DTheValue1

 row1                                         column=3Df1:c1,
timestamp=3D1412866068919,
value=3DTheValue1

 row1                                         column=3Df1:c1,
timestamp=3D1412866068894,
value=3DTheValue1

 row1                                         column=3Df1:c1,
timestamp=3D1412866068877,
value=3DTheValue1

 row1                                         column=3Df1:c1,
timestamp=3D1412866068863,
value=3DTheValue1

 row1                                         column=3Df1:c1,
timestamp=3D1412866068849,
value=3DTheValue1

 row1                                         column=3Df1:c1,
timestamp=3D1412866068834,
value=3DTheValue1

1 row(s) in 0.3110 seconds

hbase(main):022:0> flush 't1'
0 row(s) in 0.3340 seconds

hbase(main):023:0> scan 't1', {RAW =3D> true, VERSIONS =3D> 10}
ROW
COLUMN+CELL

 row1                                         column=3Df1:c1,
timestamp=3D1412866068992,
value=3DTheValue1

1 row(s) in 0.3410 seconds


2014-10-08 19:17 GMT-04:00 Andrew Purtell <apurtell@apache.org>:

> =E2=80=8B=E2=80=8B=E2=80=8BThe 2nd HBase 0.98.7 release candidate (RC1) i=
s available for download
> at http://people.apache.org/~apurtell/0.98.7RC1/ and Maven artifacts are
> also available in the temporary repository
> https://repository.apache.org/content/repositories/orgapachehbase-1042/
>
> Signed with my code signing key D5365CCD.
>
> The issues resolved in this release can be found here:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=3D123107=
53&version=3D12327560
>
>
> Please try out the candidate and vote +1/-1 by midnight Pacific Time (00:=
00
> -0800 GMT) on =E2=80=8BOctober =E2=80=8B1=E2=80=8B5=E2=80=8B =E2=80=8Bon =
whether or not we should release this as=E2=80=8B
> =E2=80=8B0.98.7. Three +1 votes from PMC will be required to release.
> =E2=80=8B=E2=80=8B
> --
> Best regards,
>
>    - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)=E2=80=8B
>

--001a11c1f0227c76a805058a99d4--