Alternatively you can use clustering columns to store very big collections.
Beware of not making a row too wide though (use bucketing) Le 23 janv. 2014 04:29, "Manoj Khangaonkar" <khangaon...@gmail.com> a écrit : > Thanks. I guess I can work around by maintaining hour_counts (which will > have fewer items) and adding the hour counts to > get day counts. > > regards > > > On Wed, Jan 22, 2014 at 7:15 PM, Robert Wille <rwi...@fold3.com> wrote: > >> I didn’t read your question properly. Collections are limited to 64K >> items, not 64K bytes per item. >> >> From: Manoj Khangaonkar <khangaon...@gmail.com> >> Reply-To: <user@cassandra.apache.org> >> Date: Wednesday, January 22, 2014 at 7:17 PM >> To: <user@cassandra.apache.org> >> Subject: Any Limits on number of items in a collection column type >> >> Hi, >> >> On C* 2.0.0. 3 Node cluster. >> >> I have a column daycount list<BigInt>. The column is storing a count. >> Every few secs a new count is appended. The total count for the day is the >> sum of all items in the list. >> >> My application logs indicate I wrote about 110000 items to the column for >> a particular row. Assume row key is day_timestamp. >> >> But when I do a read on the column I get back a list with only 43000 >> items. Checked with both java driver and CQL. >> >> There are no errors or exceptions anywhere. >> >> There is this statement in the WIKI "Collection values may not be larger >> than 64K". I assume this refers to 1 item in a collection. >> >> Has anyone else seen an issue like this ? >> >> regards >> >> MJ >> >> >> -- >> http://khangaonkar.blogspot.com/ >> > > > > -- > http://khangaonkar.blogspot.com/ >
