[
https://issues.apache.org/jira/browse/CASSANDRA-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremiah Jordan updated CASSANDRA-8616:
---------------------------------------
Description:
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.
sstablescrub, sstableverify, and other sstable tools have the same issue.
was: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.
> sstable tools 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
> Fix For: 2.1.x, 2.2.x, 3.0.x, 3.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.
> sstablescrub, sstableverify, and other sstable tools have the same issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
