RE: data modeling qu: use a Map datatype, or just simple rows... ?

2020-10-01 Thread Durity, Sean R
mailto:user@cassandra.apache.org>>; Attila Wind mailto:attila.wind@swf.technology>> Subject: Re: data modeling qu: use a Map datatype, or just simple rows... ? Don't really see a difference in two options. Won't the partitioner run on user id and create a hash for you? Unless

Re: data modeling qu: use a Map datatype, or just simple rows... ?

2020-09-19 Thread Rahul Singh
with natural string keys like “email.” Best regards, Rahul Singh From: Sagar Jambhulkar Sent: Saturday, September 19, 2020 6:45:25 AM To: user@cassandra.apache.org ; Attila Wind Subject: Re: data modeling qu: use a Map datatype, or just simple rows... ? Don't really see a difference in two op

Re: data modeling qu: use a Map datatype, or just simple rows... ?

2020-09-19 Thread Sagar Jambhulkar
Don't really see a difference in two options. Won't the partitioner run on user id and create a hash for you? Unless your hash function is better than partitioner. On Fri, 18 Sep 2020, 21:33 Attila Wind, wrote: > Hey guys, > > I'm curious about your experiences regarding a data modeling question

Re: data modeling qu: use a Map datatype, or just simple rows... ?

2020-09-18 Thread onmstester onmstester
I used Cassandra Set (no experience with map ), and one thing for sure is that with Cassandra collections you are limited to a few thousands entry per row (less than 10K for better performance) Sent using https://www.zoho.com/mail/ On Fri, 18 Sep 2020 20:33:21 +0430 Attila Wind wrote