[RESULT}[VOTE] HBase Thirdparty 2.2.0 RC1

2019-04-02 Thread Stack
With 4 binding +1s, the vote passes. Thanks to all who voted. Let me push this out. S On Sat, Mar 30, 2019 at 2:03 PM Stack wrote: > Please consider the following as the 2.2.0 release of Apache HBase > Thirdparty. It is the second release candidate for your consideration. > > It is a year since

Re: [VOTE] HBase Thirdparty 2.2.0 RC1

2019-04-01 Thread Shekhar Dhotre
Sure ,I will repost question and logs with new thread . Thanks On Mon, 1 Apr 2019 at 11:59 PM, Stack wrote: > Shekar: > > You put your note on a VOTE thread. Please redo your query in its own > thread to hbase dev. > > Can you paste some log when you redo your message on the dev list? > >

Re: [VOTE] HBase Thirdparty 2.2.0 RC1

2019-04-01 Thread Stack
Shekar: You put your note on a VOTE thread. Please redo your query in its own thread to hbase dev. Can you paste some log when you redo your message on the dev list? Thanks, S On Mon, Apr 1, 2019 at 12:33 AM Shekhar Dhotre < shekhar.dho...@clairvoyantsoft.com> wrote: > Hi All , > I have a

Re: [VOTE] HBase Thirdparty 2.2.0 RC1

2019-04-01 Thread Peter Somogyi
+1 Checked signature, checksum Built from source Ran Apache Rat check Ran HBase master tests using this RC Checked CHANGES and RELEASENOTES On Sat, Mar 30, 2019 at 10:14 PM Stack wrote: > Please consider the following as the 2.2.0 release of Apache HBase > Thirdparty. It is the second release

Re: [VOTE] HBase Thirdparty 2.2.0 RC1

2019-04-01 Thread Yu Li
+1 (binding) Checked sigs and sums: OK Built from src: OK Minor: >From dev_files/make_rc.sh we are using "git archive" instead of "maven package assembly:single", thus producing more files as listed below. Is this on purpose? Thanks. hbase-thirdparty-2.2.0/.gitignore

Re: [VOTE] HBase Thirdparty 2.2.0 RC1

2019-04-01 Thread Shekhar Dhotre
Hi All , I have a cluster which is setup to replicate to GCP . In the log its showing cluster ID null so found this document which shows how to setup cluster ID .but that is for a third party product called FusionInsight Manager.

Re: [VOTE] HBase Thirdparty 2.2.0 RC1

2019-03-31 Thread Stack
+1 from me because HBASE-22139 "Pass 2.2.0RC1 though hbase qa test suite" passed. S On Sat, Mar 30, 2019 at 2:03 PM Stack wrote: > Please consider the following as the 2.2.0 release of Apache HBase > Thirdparty. It is the second release candidate for your consideration. > > It is a year since

Re: [VOTE] HBase Thirdparty 2.2.0 RC1

2019-03-31 Thread Duo Zhang
+1(binding) Checked sigs and sums: OK Built from src: OK Compared the sizes of jars with 2.1.0: Seems fine. And we also got a green build in HBASE-22139, which is good. Stack 于2019年3月31日周日 上午9:59写道: > And the maven link is > >

Re: [VOTE] HBase Thirdparty 2.2.0 RC1

2019-03-30 Thread Stack
And the maven link is https://repository.apache.org/content/repositories/orgapachehbase-1299 , not 1297 [1]. Thanks, S 1. I built 1297 w/ jdk10. ByteBuffer in jdk10 doesn't have a position method. It made an unrelated test fail when I tried 1297 against the tip of hbase branch-2.2. 1299 is

Re: [VOTE] HBase Thirdparty 2.2.0 RC1

2019-03-30 Thread Stack
The release was made against tag 2.2.0RC1, not 2.2.0RC0 as it states below. S On Sat, Mar 30, 2019 at 2:03 PM Stack wrote: > Please consider the following as the 2.2.0 release of Apache HBase > Thirdparty. It is the second release candidate for your consideration. > > It is a year since our

[VOTE] HBase Thirdparty 2.2.0 RC1

2019-03-30 Thread Stack
Please consider the following as the 2.2.0 release of Apache HBase Thirdparty. It is the second release candidate for your consideration. It is a year since our 2.1.0 release. 2.2.0 updates some of our core dependencies: gson 2.8.1 -> 2.8.5 guava 22.0 -> 27.1-jre pb 3.5.1 -> 3.7.0 netty