Sorry about unclear naming scheme. I meant that if I want to index on a 
few columns simultaneously,
I create a new column with catenated values of these.

On 8/31/2011 3:10 PM, Anthony Ikeda wrote:
> Sorry to fork this topic, but in "composite indexes" do you mean as 
> strings or as "Composite()". I only ask cause we have started using 
> the Composite as rowkeys and column names to replace the use of 
> concatenated strings mainly for lookup purposes.
>
> Anthony
>
>
> On Wed, Aug 31, 2011 at 10:27 AM, Maxim Potekhin <potekhin@bnl.gov 
> <mailto:potekhin@bnl.gov>> wrote:
>
>     Plenty of comments in this thread already, and I agree with those
>     saying
>     "it depends". From my experience, a cluster with 18 spindles total
>     could not match the performance and throughput of our primary
>     Oracle server which had 108 spindles. After we upgraded to SSD,
>     things have definitely changed for the better, for Cassandra.
>
>     Another thing is that if you plan to implement "composite indexes" by
>     catenating column values into additional columns, that would
>     constitute
>     a "write" hence you'll need CPU. So watch out.
>
>
>
>     On 8/29/2011 9:15 AM, Helder Oliveira wrote:
>
>         Hello guys,
>
>         What is the type of profile of a cassandra server.
>         Are SSD an option ?
>         Does cassandra needs better CPU ou lots of memory ?
>         Are SATA II disks ok ?
>
>         I am making some tests, and i started evaluating the possible
>         hardware.
>
>         If someone already has conclusions about it, please share :D
>
>         Thanks a lot.
>
>
>