You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Cliff Gilmore (JIRA)" <ji...@apache.org> on 2016/11/04 14:33:58 UTC
[jira] [Created] (CASSANDRA-12879) sstablesplit Incorrectly Ignores
SStable Files
Cliff Gilmore created CASSANDRA-12879:
-----------------------------------------
Summary: sstablesplit Incorrectly Ignores SStable Files
Key: CASSANDRA-12879
URL: https://issues.apache.org/jira/browse/CASSANDRA-12879
Project: Cassandra
Issue Type: Bug
Components: Tools
Environment: Linux
Reporter: Cliff Gilmore
Priority: Minor
When trying to test sstablesplit on a valid sstable I see messages like
"Skipping non sstable file mc-7-big-Data.db"
This is clearly an sstable, so it looks like the parser for valid sstables is still assuming the old format.
StandaloneSplitter appears to call tryComponentFromFilename which calls fromFilename in src/java/org/apache/cassandra/io/sstable/Component.java
Checking the in Component.java I see a comment that looks like the code is looking for the old sstable file name format:
* {@code
* Filename of the form "<ksname>/<cfname>-[tmp-][<version>-]<gen>-<component>",
* }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)