cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timo Nentwig (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-2582) sstable2json: make TTL optional, possibility of incremental dumps
Date Mon, 18 Jul 2011 20:09:57 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timo Nentwig updated CASSANDRA-2582:
------------------------------------

    Comment: was deleted

(was: I didn't say that there's no alternative to loading the files into RAM :)

Anyway, actually modifying the JSON files was my first idea because patching distro code requires
me to patch it in every new version again. I did it anyway because it's a really trivial patch
and it save a lot of IO and time.)

> sstable2json: make TTL optional, possibility of incremental dumps
> -----------------------------------------------------------------
>
>                 Key: CASSANDRA-2582
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2582
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Timo Nentwig
>            Priority: Trivial
>         Attachments: nottl-and-lastmodified-0.7.5.patch, nottl-and-lastmodified.patch
>
>
> Data on live cluster is supposed to expire automatically but exported to an archive cluster
beforehand. In order to prevent expiration on the archive cluster add an option to sstable2json
to ignore TTL data. Furthermore add an lastModified option that ignores older columns for
incremental archiving.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message