So when using Redis, how do you go about updating the index? Do you serialize changes to the index i.e. when someone votes, you then update the index?
Little confused as to how to go about updating a huge index. Say you have 1 million stores, and you want to order by the top votes, how would you maintain such an index since they are being constantly voted on. On Sun, Aug 15, 2010 at 10:48 PM, Chris Goffinet <c...@chrisgoffinet.com>wrote: > Digg is using redis for such a feature as well. We use it on the MyNews - > Top in 24 hours. Since we need timestamp ordering + sorting by how many > friends touch a story. > > -Chris > > On Aug 15, 2010, at 7:34 PM, Benjamin Black wrote: > > > http://code.google.com/p/redis/ > > > > On Sat, Aug 14, 2010 at 11:51 PM, S Ahmed <sahmed1...@gmail.com> wrote: > >> For CF that I need to perform range scans on, I create separate CF that > have > >> custom ordering. > >> Say a CF holds comments on a story (like comments on a reddit or digg > story > >> post) > >> So if I need to order comments by votes, it seems I have to re-index > every > >> time someone votes on a comment (or batch it every x minutes). > >> > >> > >> Right now I think I have to pull all the comments into memory, then sort > by > >> votes, then re-write the index. > >> Are there any best-practises for this type of index? > >
