[ https://issues.apache.org/jira/browse/CASSANDRA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175070#comment-13175070 ]
Pavel Yaskevich commented on CASSANDRA-2749: -------------------------------------------- Thanks, Sylvain! We are getting really close :) Here are problems I found: - o.a.c.db.Directories comment should be updated because it still uses SSTable file name without keyspace. - o.a.c.io.sstable.SSTableReaderTest won't compile - if you start with empty data directory you get following exception and process exits {code} INFO 23:51:11,987 Upgrade from pre-1.1 version detected: migrating sstables to new directory layout ERROR 23:51:11,988 Exception encountered during startup java.lang.NullPointerException at org.apache.cassandra.db.Directories.migrateSSTables(Directories.java:416) at org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandraDaemon.java:164) at org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:360) at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:107) java.lang.NullPointerException at org.apache.cassandra.db.Directories.migrateSSTables(Directories.java:416) at org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandraDaemon.java:164) at org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:360) at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:107) Exception encountered during startup: null {code} - on snapshot doesn't create or move (from older schema) index SSTables related to CF - shouldn't old "snapshots" directory be removed after move? > fine-grained control over data directories > ------------------------------------------ > > Key: CASSANDRA-2749 > URL: https://issues.apache.org/jira/browse/CASSANDRA-2749 > Project: Cassandra > Issue Type: New Feature > Components: Core > Reporter: Jonathan Ellis > Priority: Minor > Fix For: 1.1 > > Attachments: 0001-2749-v2.patch, > 0001-Make-it-possible-to-put-column-families-in-subdirect.patch, > 0001-add-new-directory-layout.patch, > 0001-non-backwards-compatible-patch-for-2749-putting-cfs-.patch.gz, > 0002-fix-unit-tests-v2.patch, 0002-fix-unit-tests.patch, 2749.tar.gz, > 2749_backwards_compatible_v1.patch, 2749_backwards_compatible_v2.patch, > 2749_backwards_compatible_v3.patch, 2749_backwards_compatible_v4.patch, > 2749_backwards_compatible_v4_rebase1.patch, 2749_not_backwards.tar.gz, > 2749_proper.tar.gz > > > Currently Cassandra supports multiple data directories but no way to control > what sstables are placed where. Particularly for systems with mixed SSDs and > rotational disks, it would be nice to pin frequently accessed columnfamilies > to the SSDs. > Postgresql does this with tablespaces > (http://www.postgresql.org/docs/9.0/static/manage-ag-tablespaces.html) but we > should probably avoid using that name because of confusing similarity to > "keyspaces." -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira