[ https://issues.apache.org/jira/browse/CASSANDRA-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yuki Morishita updated CASSANDRA-8616: -------------------------------------- Attachment: 8161-2.0.txt This is due to the fact that loading schema writes (updates) schema version whenever it happens. (I believe the behavior hasn't changed for a while, so issue here has been around way before 2.0.10.) Also judging from the code, standalone scrub/upgradesstbale/sstablesplit behave the same. Quick work around is to add the way to load schema without updating schema version. > 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.0.13 > > 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)