> Would > appreciate feedback on them though, if you have some spare time. > Interesting? Useful? Broken? >
that is great stuff. I've ran into issues with the hard coded write buffer and I ended up having a custom client that relies on the configured hbase buffer size instead, but I think your patch covers more than what I was doing initially. thanks! esteban. > > > On Tue, May 26, 2015 at 9:54 AM, ramkrishna vasudevan < > [email protected]> wrote: > > > +1. Reg the way YCSB works, I would say the first thing that we may need > > is that the load should be evenly distributed after presplitting the > > regions. Most of the time it does not happen that way and only one among > > the RS is heavily used. > > > > Regards > > Ram > > > > On Tue, May 26, 2015 at 9:58 PM, Sean Busbey <[email protected]> > wrote: > > > > > Hi Folks! > > > > > > I've recently become a maintainer on YCSB. We're looking to get a > release > > > out in June (our first in several years). We'll probably begin release > > > candidates in a couple of weeks. > > > > > > I'd really like to improve the experience of folks using HBase; the > > current > > > state of the datastore binding leaves much to be desired. Right now, > > people > > > can't even reliably run against multiple versions of HBase. I *think* > > only > > > using 1.0+ client jars works, regardless of old/new API usage. I'll > find > > > out for sure in RC testing. > > > > > > Unfortunately, my time on the project is quickly absorbed handling > > reviews > > > and community management efforts. I know a few folks in the HBase > > community > > > have made their own changes over the last few years. If folks could > find > > > some time to rebase their forks for the current state of the master > > branch > > > and submit pull requests I'd be super grateful. > > > > > > -- > > > Sean > > > > > > > > > -- > Best regards, > > - Andy > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > (via Tom White) >
