On Fri, Dec 11, 2009 at 1:32 PM, gabriele renzi <[email protected]> wrote: > FWIW, in our current application with 0.4 we implemented in-cassandra > caching, whereas a query that reads many thousands of columns and > takes some time is cached in a separate entry > QueryCache[q]=serializedResult > and we flush it on update. > I don't see why that cant be done by cassandra itself (maybe it's > already done in 0.5)
No, but it is worth exploring. -Jonathan
