We are having a hackathon the day of during the conference. Not exclusive to the idea of having a separate hack day the day before. I know some of us are participating in the conference and can't participate in the hackathon.
Possibly, but it would look different than Don described. It would be fairly easy to write data to an existing HBase instance from Accumulo (and one can probably assume the opposite to be true). Thus, Gets/Scans would be using the HBase API.
I've thought about this a lot actually (and finally have some time to sit down and type it out). This plays into my larger idea of an automated hbase->accumulo suite. A system that moves data from one to the other is one piece, the other piece is letting existing hbase applications hit accumulo instead. Anyways...
The most efficient thing to do is to have Accumulo tablet servers speak something that a native hbase client can talk to. What's going on in a client is pretty complex, so it's not going to be as easy as writing some interfaces. I think.
The proxy idea is okay, but I think we'll see some performance problems.
The other option is to do it client side, which would mean the applications would need to be rebuilt with our "special" APIs that look the same as before, but really behind the scenes are translating it to an accumulo call. Maybe they'd have to change an import or something.
Maybe there is a larger project here, something like a bigtable API that Cassandra, HBase, and Accumulo all can sign on to supporting. Or it is just client-side code. Not sure. Then something like OpenTSDB or zipkin would just write to the bigtable API and you wouldn't have to write new code.
Lot of options... not sure which one i like. Sorry for rambling.
-d On Sun, May 11, 2014 at 8:56 PM, Donald Miner <[EMAIL PROTECTED]>wrote: Donald Miner Chief Technology Officer ClearEdge IT Solutions, LLC Cell: 443 799 7807 www.clearedgeit.com