[
https://issues.apache.org/jira/browse/CASSANDRA-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624274#comment-14624274
]
Sylvain Lebresne commented on CASSANDRA-8616:
---------------------------------------------
Agreed. The goal mid-term is to get something CASSANDRA-9587 so such tool
really act as external tools, i.e. they don't silently load a lot of the same
stuff than the server so this kind of thing cannot happen.
> sstable2json may result in commit log segments be written
> ---------------------------------------------------------
>
> Key: CASSANDRA-8616
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8616
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Reporter: Tyler Hobbs
> Assignee: Yuki Morishita
> Fix For: 2.1.x
>
> Attachments: 8161-2.0.txt
>
>
> There was a report of sstable2json causing commitlog segments to be written
> out when run. I haven't attempted to reproduce this yet, so that's all I
> know for now. Since sstable2json loads the conf and schema, I'm thinking
> that it may inadvertently be triggering the commitlog code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
