On Sat, Nov 4, 2017 at 1:45 AM, Jean-Marc Spaggiari <jean-m...@spaggiari.org > wrote:
> Folks, are you able to run the tests? > > I'm trying to run this: > > mvn test -P runAllTests -Dsurefire.secondPartThreadCount=2 > -Dtest.build.data.basedirectory=/ram4G > > > But I'm not able to get it running completely. It always fails somewhere, > never in the same place. How are you running the tests, if you are? > > Else: > MD5 and SHA files correct for both Binary and Source > *changes.txt file doesn't seems correct. Missing last versions* > *checkstyle.html doesn't seems to be accurate. Reports 0 files.* > Documetation ok. > > Will run more tests later when I can get runAllTests pass... > Test fail JMS. We have to fix all for beta-1. I should have said this in the announcement. Thanks for giving it a go boss. S > > 2017-11-03 3:32 GMT-04:00 Yung-An He <mathst...@gmail.com>: > > > +1 non-binding > > > > Checked MD5 : OK > > Download the bin tarball : OK > > Start from bin tar with cluster mode via docker container: OK > > Import data with 100 million rows and 10 columns to table via ImportTsv: > OK > > Execute basic command via `hbase shell`: OK > > > > > > > > > > 2017-11-02 5:02 GMT+08:00 Mike Drob <mad...@cloudera.com>: > > > > > +1 > > > > > > Verified sigs and hashes. > > > Src tar matches git tag. > > > Able to build from src tar w/ hadoop 2 & 3 > > > Able to start from bin tar, verified basic functionality. > > > > > > Filed HBASE-19151 for some warning messages on shell startup. > > > Failed to start with Java9, but didn't expect this to work anyway. > > > > > > On Wed, Nov 1, 2017 at 1:38 PM, Artem Ervits <artemerv...@gmail.com> > > > wrote: > > > > > > > +1 > > > > > > > > Checked md5 > > > > ran LTT tool with 10k rows > > > > ran PE tool with 6M rows > > > > executed counter in hbase shell > > > > > > > > > > > > > > > > On Wed, Nov 1, 2017 at 1:18 PM, Ted Yu <yuzhih...@gmail.com> wrote: > > > > > > > > > +1 > > > > > > > > > > Checked signatures > > > > > Built from source > > > > > Ran load test tool with 1 mil rows. > > > > > > > > > > On Wed, Nov 1, 2017 at 7:17 AM, Stack <st...@duboce.net> wrote: > > > > > > > > > > > The first release candidate for HBase 2.0.0-alpha4 is up at: > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0- > > > alpha4RC0/ > > > > > > > > > > > > Maven artifacts are available from a staging directory here: > > > > > > > > > > > > https://repository.apache.org/content/repositories/orgapach > > > > ehbase-1178 > > > > > > > > > > > > All was signed with my key at 8ACC93D2 [1] > > > > > > > > > > > > I tagged the RC as 2.0.0-alpha4RC0 > > > > > > (5c4b985f89c99cc8b0f8515a4097c811a0848835) > > > > > > > > > > > > hbase-2.0.0-alpha4 is our fourth alpha release along our march > > toward > > > > > > hbase-2.0.0. It includes all that was in previous alphas (new > > > > assignment > > > > > > manager, offheap read/write path, in-memory compactions, etc.), > but > > > > had a > > > > > > focus on "Coprocessor Fixup": We no longer pass Coprocessors > > > > > > InterfaceAudience.Private parameters and we cut down on the > access > > > and > > > > > > ability to influence hbase core processing (See [2] on why the > > > radical > > > > > > changes in Coprocessor Interface). If you are a Coprocessor > > developer > > > > or > > > > > > have Coprocessors to deploy on hbase-2.0.0, we need to hear about > > > your > > > > > > experience now before we make an hbase-2.0.0 beta. > > > > > > > > > > > > hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production > > > preview > > > > > of > > > > > > what hbase-2.0.0 will look like. It is meant for devs and > > > downstreamers > > > > > to > > > > > > test drive and flag us early if we messed up anything ahead of > our > > > > > rolling > > > > > > GAs. > > > > > > > > > > > > The list of features addressed in 2.0.0 so far can be found here > > [3]. > > > > > There > > > > > > are thousands. The list of ~2k+ fixes in 2.0.0 exclusively can be > > > found > > > > > > here [4] (My JIRA JQL foo is a bit dodgy -- forgive me if > > mistakes). > > > > > > > > > > > > I've updated our overview doc. on the state of 2.0.0 [6]. > > > 2.0.0-beta-1 > > > > > will > > > > > > be our next release. Its theme is the "Finishing up 2.0.0" > release. > > > > Here > > > > > is > > > > > > the list of what we have targeted for beta-1 [5]. Check it out. > > Shout > > > > if > > > > > > there is anything missing. We may do a 2.0.0-beta-2 if a need. > > We'll > > > > see. > > > > > > > > > > > > Please take this alpha for a spin especially if you are a > > Coprocessor > > > > > > developer or have a Coprocessor you want to deploy on > hbase-2.0.0. > > > > Please > > > > > > vote on whether it ok to put out this RC as our first alpha (bar > is > > > low > > > > > for > > > > > > an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the > VOTE > > be > > > > > open > > > > > > for 72 hours (Saturday) > > > > > > > > > > > > Thanks, > > > > > > Your 2.0.0 Release Manager > > > > > > > > > > > > 1. http://pgp.mit.edu/pks/lookup?op=get&search= > 0x9816C7FC8ACC93D2 > > > > > > 2. Why CPs are Incompatible: > > > > > > https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_ > > > > > > ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj > > > > > > 3. https://goo.gl/scYjJr > > > > > > 4. https://goo.gl/tMHkYS > > > > > > 5. https://issues.apache.org/jira/projects/HBASE/versions/ > 12340861 > > > > > > 6. > > > > > > https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_ > > > > > > ktczrlKHK8N4SZzs/ > > > > > > > > > > > > > > > > > > > > >
