[
https://issues.apache.org/jira/browse/CASSANDRA-15813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
maxwellguo updated CASSANDRA-15813:
-----------------------------------
Change Category: Operability
Complexity: Normal
Fix Version/s: 4.x
3.11.x
2.2.x
2.1.x
Platform: Linux (was: All)
Priority: Low (was: Normal)
Status: Open (was: Triage Needed)
> Cassandra commitlog dump
> -------------------------
>
> Key: CASSANDRA-15813
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15813
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Commit Log
> Reporter: maxwellguo
> Assignee: maxwellguo
> Priority: Low
> Fix For: 2.1.x, 2.2.x, 3.11.x, 4.x
>
>
> when we do backup using commitlog or other cases using commitlog ,we may want
> to know the data contains in commitlog . For other nosql like hbase, they
> also support the tool to show the contents in WAL log(Hlog). so I think a
> tool like sstabledump is needed for commitlog .
> For me , I think the input is the commitlog's absolute path, the out put
> format may be json depends on the commitlog version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
