[ https://issues.apache.org/jira/browse/CASSANDRA-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Meyer updated CASSANDRA-6028: ------------------------------------ Fix Version/s: (was: 1.2.9) (was: 2.0) > Default sstable output size not respected when running sstablesplit > ------------------------------------------------------------------- > > Key: CASSANDRA-6028 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6028 > Project: Cassandra > Issue Type: Bug > Environment: java version "1.7.0_40" > Java(TM) SE Runtime Environment (build 1.7.0_40-b43) > Java HotSpot(TM) 64-Bit Server VM (build 24.0-b56, mixed mode) > Reporter: Daniel Meyer > Priority: Minor > > Run sstablesplit -h: > usage: sstablessplit [options] <filename> [<filename>]* > -- > Split the provided sstables files in sstables of maximum provided file > size (see option --size). > -- > Options are: > --debug display stack traces > -h,--help display this help message > --no-snapshot don't snapshot the sstables before splitting > -s,--size <size> maximum size in MB for the output sstables (default: > 50) > -v,--verbose verbose output > From the help message we expect the default size to be 50 MB. > repro steps: > supply any sstable of any size to sstablesplit but leave out the --size > option. > Expected: should split sstable into 50MB sstables > Actual: > Pre-split sstables snapshotted into snapshot pre-split-1379086801768 > Error splitting > SSTableReader(path='./Keyspace1/Standard1/Keyspace1-Standard1-ic-15-Data.db'): > Invalid target size for SSTables, must be > 0 (got: 0) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira