> later i will need to apply filter to that data,
Sounds like a read query you should support by denormalising the data.
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 25/08/2011, at 10:50 PM, Helder Oliveira wrote:
> Hello,
>
Hello,
thanks for your time.
I have suggested a SCF but i am still testing the system with CF, making some
tests and testing the data flow ( insert / select ).
Making subdata as JSON already came into my mind, but it's not possible because
later i will need to apply filter to that data, and if
I normally suggest trying a model with Standard CF's first as there are some
down sides to super CF's. If you know there will only be a few sub columns
there are probably OK (see
http://wiki.apache.org/cassandra/CassandraLimitations). Your alternative design
is fine. Test it out and see what wo
Thanks Indranath Ghosh for your tip!
I will continue here the question.
Aaron, i have read your suggestion and tried to design your suggestion and i
have one question regarding it.
Let's forget for now the Requests and Events!
Just keep the Visitants and the Sessions.
My goal is when having a
Lets start with something quick and simple, all standard Column Families…
Visitant CF
key: id
column name: property name
column value: property value
Visitant Sessions CF
key: visitant id
column name: session id
column value: none
Session CF
key: session_id
column_name: property value
colum
Hello all,
i have a SQL structure like this:
Visitant ( has several properties )
Visitant has many Sessions
Sessions ( has several properties )
Sessions has many Requests ( has several properties )
Sessions has many Events ( has several properties )
i have read a lot and still confused how to p
