The latter.
On Thu, Apr 21, 2011 at 1:24 AM, Constantin Teodorescu
wrote:
> Thank you very much Ellis, I heard about Brisk two weeks ago and I'm already
> checking DataStax web site twice a day waiting for Brisk to come.
> It seems that it will be a good solution for us.
> Once more question plea
Thank you very much Ellis, I heard about Brisk two weeks ago and I'm already
checking DataStax web site twice a day waiting for Brisk to come.
It seems that it will be a good solution for us.
Once more question please: the Brisk way of operation need to transfer
intermediate data from Cassandra st
You want to run map/reduce jobs for your use case. You can already do
this with Cassandra (http://wiki.apache.org/cassandra/HadoopSupport),
and DataStax is introducing Brisk soon to make it easier:
http://www.datastax.com/products/brisk
On Wed, Apr 20, 2011 at 9:36 PM, Jonathan Ellis wrote:
> CQL
CQL changes the API, that is all.
On Wed, Apr 20, 2011 at 5:40 PM, Constantin Teodorescu
wrote:
> My use case is as follows: we are using in 70% of the jobs information
> retrieval using keys, column names and ranges and up to now, what we have
> tested suits our need.
> However, the rest of 30%
My use case is as follows: we are using in 70% of the jobs information
retrieval using keys, column names and ranges and up to now, what we have
tested suits our need.
However, the rest of 30% of the jobs involve full sequential scan of all
records in the database.
I found some web pages describin