Re: Schema advice/help

2012-03-28 Thread Maciej Miklas
correct - I see also no other solution for this problem On Thu, Mar 29, 2012 at 1:46 AM, Guy Incognito wrote: > well, no. my assumption is that he knows what the 5 itemTypes (or > appropriate corresponding ids) are, so he can do a known 5-rowkey lookup. > if he does not know, then agreed, my p

Re: Schema advice/help

2012-03-28 Thread Guy Incognito
well, no. my assumption is that he knows what the 5 itemTypes (or appropriate corresponding ids) are, so he can do a known 5-rowkey lookup. if he does not know, then agreed, my proposal is not a great fit. could do (as originally suggested) userId -> itemType:activityId if you want to keep

Re: Schema advice/help

2012-03-28 Thread Maciej Miklas
yes - but anyway in your example you need "key range quey" and that requires OOP, right? On Tue, Mar 27, 2012 at 5:13 PM, Guy Incognito wrote: > multiget does not require OPP. > > On 27/03/2012 09:51, Maciej Miklas wrote: > > multiget would require Order Preserving Partitioner, and this can lea

Re: Schema advice/help

2012-03-27 Thread Guy Incognito
multiget does not require OPP. On 27/03/2012 09:51, Maciej Miklas wrote: multiget would require Order Preserving Partitioner, and this can lead to unbalanced ring and hot spots. Maybe you can use secondary index on "itemtype" - is must have small cardinality: http://pkghosh.wordpress.com/201

Re: Schema advice/help

2012-03-27 Thread Ertio Lew
@R. Verlangen: You are suggesting to keep a single row for all activities & read all the columns from the row & then filter, right!? If done that way (instead of keeping it in 5 rows) then I would need to retrieve 100s-200s of columns from single row rather than just 50 columns if I keep in 5 rows

Re: Schema advice/help

2012-03-27 Thread R. Verlangen
You can just get a slice range with as start "userId:" and no end. 2012/3/27 Maciej Miklas > multiget would require Order Preserving Partitioner, and this can lead to > unbalanced ring and hot spots. > > Maybe you can use secondary index on "itemtype" - is must have small > cardinality: > http:/

Re: Schema advice/help

2012-03-27 Thread Maciej Miklas
multiget would require Order Preserving Partitioner, and this can lead to unbalanced ring and hot spots. Maybe you can use secondary index on "itemtype" - is must have small cardinality: http://pkghosh.wordpress.com/2011/03/02/cassandra-secondary-index-patterns/ On Tue, Mar 27, 2012 at 10:10 AM

Re: Schema advice/help

2012-03-27 Thread Guy Incognito
without the ability to do disjoint column slices, i would probably use 5 different rows. userId:itemType -> activityId then it's a multiget slice of 10 items from each of your 5 rows. On 26/03/2012 22:16, Ertio Lew wrote: I need to store activities by each user, on 5 items types. I always wan