Thanks for this update.
After another day at work, and more reading into the Cassandra's underlying
model, I think the problem i am encountering is less due to HBase and more
with user error and a highly faulty cluster.
Cassandra's clean api and integration with thrift were the two biggest
factor
Status: Fixed, Fix version: 7.0 beta 1 means it's in the beta1 that
was just released, although
https://issues.apache.org/jira/browse/CASSANDRA-1315 is open to change
the API slightly. Either way, it won't be backported to 0.6.
But you can write to Cassandra from the Hadoop job just fine w/o an
O
I am curious to know the reasons you are moving away from HBase. It would be
great if you could state them.
On Sun, Aug 15, 2010 at 4:24 PM, Keith Stevens wrote:
> Hello,
>
> I'm currently working on a project that is using HBase and Hadoop, but i'm
> currently looking into alternatives to HBase.
Hello,
I'm currently working on a project that is using HBase and Hadoop, but i'm
currently looking into alternatives to HBase. Cassandra seems to be the
next best replacement, or perhaps a better replacement, except that the
stable release is lacking support for hadoop jobs writing to Cassandra.
