[jira] [Commented] (CASSANDRA-4392) Create a tool that will convert a commit log into a series of readable CQL statements

["Jeremy Hanna (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403340#comment-13403340 ] 

Jeremy Hanna commented on CASSANDRA-4392:
-----------------------------------------

Since this is going to apply to several nodes, it might be nice to have a way to aggregate the CQL statements as well and then apply them in bulk at the cluster again.

It would seem that some information is lost after it gets to the commitlog, however.  So the consistency level that something is written at is probably not available.  The CQL statement might do USING ALL so that it errs on the side of make it apply to everything.  Or make that configurable.
                
> Create a tool that will convert a commit log into a series of readable CQL statements
> -------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-4392
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4392
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Jeremy Hanna
>
> To enable a case of point in time recovery not currently handled by cassandra, it would be great to have a way to convert a commit log into a series of readable CQL statements.
> Currently one is able to do recovery up to current sstables, or with CASSANDRA-3690, additionally apply the current commit logs in their entirety.  The one missing case is to say that I want to recover to a point in time before I did stupid/damaging operation X.  That needs visibility into the commit logs.
> I thought the simplest way to do this would be to have a tool that converts commit logs into readable CQL statements so they could be selectively applied.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira