One suggestion: Can we move from simplistic scenarios towards more realistic ones? When client - server interaction can involve server-side processing as well? HBase is good at that.
One example: credit card fraud application which usually, for every transaction, involves analyzing client TXs for past xx months as well as verification of a vendor (simplistic description but nevertheless ...)? Another example: sensor data stream -> server calculates and updates multiple aggregates for every sensor reading. -Vlad On Tue, May 26, 2015 at 10:03 AM, Sean Busbey <[email protected]> wrote: > I should note that the other maintainer and I are planning on a monthly > release cadence going forward, so folks need not worry that this will be > the only release gate for years to come. > > On Tue, May 26, 2015 at 11:28 AM, 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 > > > > > > -- > Sean >
