[
https://issues.apache.org/jira/browse/CASSANDRA-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143867#comment-15143867
]
Yuki Morishita commented on CASSANDRA-8616:
-------------------------------------------
I wrote dirty workaround patch: https://github.com/yukim/cassandra/tree/8616-2.1
Basically added flag to disable CommitLogAllocator so directories/files are not
created.
We cannot use Config.setClientMode for that because it causes another
problems(basically, we cannot use ColumnFaimlyStore in client mode).
At first, I wrote offline schema loader that constructs schema from schema_*
SSTables. But, offline tools just use ColumnFamilyStore everywhere, I needed to
rewrite everything. So I end up above hack.
I can save it for later, probably at the time CASSANDRA-7464 is in.
If the change looks good, I will work for other branches.
> 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
> Assignee: Yuki Morishita
> 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)
