You can refer to the Data Modelling guide here: 
It includes several things you've mentioned (namely, range queries and dynamic tables). 

Also, it seems that it'd be useful for you to use indexes, and performing filtering (for things related to "give me everything about symbol X"), for that you can refer to K/V operations guide: (range query section) and (filtering section). 

It looks that data model fits really well to what Cassandra allows. Especially in financial data, it sounds like you can use your "symbol" as a partition key, which opens up a wild range of possibilities for querying. 

On Fri, Jun 7, 2013 at 9:16 PM, Jake Luciani <> wrote:
We have built a similar system, you can ready about our data model in CQL3 here:

We are going to be presenting a similar talk next week at the cassandra summit.

On Fri, Jun 7, 2013 at 12:34 PM, Davide Anastasia <> wrote:


I am trying to build the storage of stock prices in Cassandra. My queries are ideally of three types:

- give me everything between time A and time B;

- give me everything about symbol X;

- give me everything of type Y;

…or an intersection of the three. Something I will be happy doing is:

- give me all the trades about APPL between 7:00am and 3:00pm of a certain day.


However, being a time series, I will be happy to retrieve the data in ascending order of timestamp (from 7:00 to 3:00).


I have tried to build my table with the timestamp (as timeuuid) as primary key, however I cannot manage to get my data in order and and “order by” in CQL3 raise an error and doesn’t perform the query.


Does anybody have any suggestion to get a good design the fits my queries?




alex p