Hmm. Hadn't thought about using a collection. Might be able to get away with a map. Have to find out more about the origins of these relationships.
I don't think XML gives any advantage over JSON, but it is another possibility. Les On Wed, Jan 22, 2014 at 7:43 AM, chandra Varahala < hadoopandcassan...@gmail.com> wrote: > Hello, > > You can implement relations in couple of ways, JSON/XML and CQL > collection Classes. > > Thanks > Chandra > > > On Tue, Jan 21, 2014 at 8:58 PM, Les Hartzman <lhartz...@gmail.com> wrote: > >> True. Fortunately though in this application, the data is >> write-once/read-many. So that is one bullet I would dodge! >> >> Les >> >> >> On Tue, Jan 21, 2014 at 5:34 PM, Patricia Gorla < >> patri...@thelastpickle.com> wrote: >> >>> Hey, >>> >>> One thing to keep in mind if you want to go the serialized JSON route, >>> is that you will need to read out the data each time you want to do an >>> update. >>> >>> Cheers, >>> Patricia >>> >>> >>> On Tuesday, January 21, 2014, Les Hartzman <lhartz...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> I'm looking to move from a relational DB to Cassandra. I just found >>>> that there are intra-table relationships in one table where the ids of the >>>> related rows are saved in a 'parent' row. >>>> >>>> How can these kinds of relationships be handled in Cassandra? I'm >>>> thinking that if the individual rows need to live on their own, perhaps I >>>> should store the data as serialized JSON in its own column of the parent. >>>> >>>> All thoughts appreciated! >>>> >>>> Thanks. >>>> >>>> Les >>>> >>>> >>> >>> -- >>> Patricia Gorla >>> @patriciagorla >>> >>> Consultant >>> Apache Cassandra Consulting >>> http://www.thelastpickle.com <http://thelastpickle.com> >>> >>> >> >
