What makes cassandra a poor choice is the fact that, you can't use a keyrange as input for the map phase for Hadoop.
On Tue, May 11, 2010 at 1:52 PM, Paulo Gabriel PoiatiSure.
> - First of all, my first thoughts is to have two CF one for raw client
> request (~10 millions++ per day) and other for aggregated metrics in some
> defined inteval time like 1min, 5min, 15min... Is this a good approach ?
The problem with OPP isn't overhead (it is lower-overhead than RP) but
> - It is a good idea to use a OrderPreservingPartitioner ? To maintain the
> order of my requests in the raw data CF ? Or the overhead is too big.
the tendency to have hotspots in sequentially-written data.
You'll have to do some load testing to see.
> - Initially the cluster will contain only three nodes, is it a problem (to
> few maybe) ?
Map/Reduce is usually better than rolling your own because it
> - I think the best way to do the aggregation job is through a hadoop
> MapReduce job. Right ? Is there any other way to consider ?
parallelizes for you.
Nothing here makes me think "Cassandra is a poor choice."
> - Is really Cassandra suitable for it ? Maybe HBase is better in this case?
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support