Tony hi, Yes, in some scenarios (e.g. a DW), e.g. absence of proper PKs or indexes (just too hard to envision, you need to think of future queries 1st) getting thru large volumes of data makes NoSQL IMHO hard to fit in.
But you have other choices: 1) pagination or 2) slice queries. Both of that is covered here: http://pkghosh.wordpress.com/2012/03/04/cassandra-range-query-made-simple/ Hope that helps. /Arthur From: Tony Anecito Sent: Wednesday, June 26, 2013 1:55 PM To: Robert Coli ; Users-Cassandra Subject: Re: Creating an "Index" column... Hi Robert, Actually that is what I did. I did that in my RDMS data model. In Cassandra or NOSQL without join or nested selects I have to do two queries. Also, since batching is not supported on the server side which makes the performance worse. I just started learning Cassandra but I am learning fast and there are some challenges when moving to a new data model driven by these factors. Regards, -Tony -------------------------------------------------------------------------------- From: Robert Coli <rc...@eventbrite.com> To: user@cassandra.apache.org; Tony Anecito <adanec...@yahoo.com> Sent: Wednesday, June 26, 2013 11:32 AM Subject: Re: Creating an "Index" column... On Wed, Jun 26, 2013 at 10:20 AM, Tony Anecito <adanec...@yahoo.com> wrote: > Never mind I figured it out. I found it via a search for Secondary indexes. In general unless you actually need atomic update of the row and its secondary index, you are probably better off creating your own pseudo secondary index column family. =Rob
