I think it is still to young, and have to wait or write your self the "graphical console", at least, I don't find any until now.
On Wed, Apr 14, 2010 at 10:04 AM, Bertil Chapuis <bchap...@gmail.com> wrote: > I'm also new to cassandra and about the same question I asked me if using > super columns with one key per version was feasible. Is there limitations to > this use case (or better practices)? > > Thank you and best regards, > > Bertil Chapuis > > On 14 April 2010 09:45, Sylvain Lebresne <sylv...@yakaz.com> wrote: > >> > I am new to using cassandra. In the documentation I have read, >> understand, >> > that as in other non-documentary databases, to update the value of a >> > key-value tuple, this new value is stored with a timestamp different but >> > without entirely losing the old value. >> > I wonder, as I can restore the historic values that have had a >> particular >> > field. >> >> You can't. Upon update, the old value is lost. >> From a technical standpoint, it is true that this old value is not >> deleted (from disk) >> right away, but it is deleted eventually by compaction (and you don't >> really control >> when the compactions occur). >> >> -- >> Sylvain >> > >
