I've started looking at something like this for the major read/write APIs for HBase and Accumulo in Kite.
One difference is that I'd prefer to eventually get to a common API that can be backed by either HBase 0.98+ or Accumulo. -- Sean On May 11, 2014 6:34 PM, "David Medinets" <[email protected]> wrote: > Please define "hbase commands". > > > On Sun, May 11, 2014 at 7:29 PM, Donald Miner <[email protected]>wrote: > >> Crazy/bad idea I've had before.... we could develop a hbase->accumulo >> proxy that receives basic hbase commands and then writes out accumulo. >> >> On May 11, 2014, at 4:57 PM, Eric Newton <[email protected]> wrote: >> >> It is being maintained. I have tried very hard not to modify the core >> OpenTSDB to support it. But, it would be nice if we could define a >> storage-independent layer to which it could adhere. >> >> I don't believe the OTSDB team is interested, but a basic scalable >> back-end abstraction would be nice. As would a standard java build >> environment, but that doesn't seem to be wanted, either. >> >> We could work towards a common storage abstraction, which would be a >> reasonable request. >> >> Zipkin does a good job of being storage independent. I would work >> towards their model. >> >> -Eric >> >> On May 11, 2014 10:28 AM, "Arshak Navruzyan" <[email protected]> wrote: >> >>> I noticed Eric Newton's opentsdb adapter for Accumulo. Is this still >>> being maintained? >>> >>> https://github.com/ericnewton/accumulo-opentsdb >>> >>> Also wondering if the StumbleUpon folks are willing to merge it in as an >>> alternative to HBase back end. >>> >>> Thanks >>> >>> Arshak >>> >> >
