Awesome. Thanks a lot Graham. Will use the clock timestamp for versioning :)
On Wed, Jan 21, 2015 at 2:02 PM, graham sanderson <gra...@vast.com> wrote: > I believe you can use “USING TIMESTAMP XXX” with your inserts which will > set the actual cell write times to the timestamp you provide. Then at least > on read you’ll get the “latest” value… you may or may not incur an actual > write of the old data to disk, but either way it’ll get cleaned up for you. > > > On Jan 21, 2015, at 1:54 AM, Pandian R <pandian4m...@gmail.com> wrote: > > > > Hi, > > > > I just wanted to know if there is any kind of versioning system in > cassandra while indexing new data(like the one we have for ElasticSearch, > for example). > > > > For example, I have a series of payloads each coming with an id and > 'updatedAt' timestamp. I just want to maintain the latest state of any > payload for all the ids ie, index the data only if the current payload has > greater 'updatedAt' than the previously stored timestamp. I can do this > with one additional self-lookup, but is there a way to achieve this without > overhead of additional lookup ? > > > > Thanks ! > > > > -- > > Regards, > > Pandian > > -- Regards, Pandian