For CF that I need to perform range scans on, I create separate CF that have
custom ordering.
Say a CF holds comments on a story (like comments on a reddit or digg story
post)
So if I need to order comments by votes, it seems I have to re-index every
time someone votes on a comment (or batch it
I'm using Cassandra 0.6.3 but plan on switching to 0.7.0 later. While
compiling I have a copy of the storage-conf.xml from the running cluster :-)
On Fri, Aug 13, 2010 at 9:51 PM, Stu Hood stu.h...@rackspace.com wrote:
Still I get an exception which I cannot explain where it comes
from
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
On Sunday, August 15, 2010, S Ahmed sahmed1...@gmail.com wrote:
For CF that I need to perform range scans on, I create separate CF that have
custom ordering.
Say a CF holds comments on a story (like comments on a reddit or digg story
post)
So if I need to order comments by votes, it seems I
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 fozzietheb...@gmail.comwrote:
Hello,
I'm currently working on a project that is using HBase and Hadoop, but i'm
currently looking into
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
http://code.google.com/p/redis/
On Sat, Aug 14, 2010 at 11:51 PM, S Ahmed sahmed1...@gmail.com wrote:
For CF that I need to perform range scans on, I create separate CF that have
custom ordering.
Say a CF holds comments on a story (like comments on a reddit or digg story
post)
So if I need
ranges are always in token order. this is why ranges with a start and
end are only useful with OrderPreservingPartioner, where token order
is defined to be key order.
On Fri, Aug 13, 2010 at 11:47 AM, Mark static.void@gmail.com wrote:
Keys are indexed in Cassandra but are they ordered? If