[
https://issues.apache.org/jira/browse/CASSANDRA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-2749:
----------------------------------------
Attachment: 0002-fix-unit-tests-v2.patch
0001-2749-v2.patch
Patch attached (0001-2749-v2.patch and 0002-fix-unit-tests-v2.patch) that:
# only support the new layout with sstables in cf directories
# migrate automagically files the first time
# adds the keyspace into the file name (to not rely on the directory sstables
are in)
# limit keyspace and cf names to 32 characters
During the initial upgrade, we also check if the user would be fine with the
current keyspace and cf name. If not, we just refuse to start. I hope this
won't happen to anyone because renaming a CF/Keyspace in a rolling fashion is
not something fun (or even possible for that matter). Note that this check
don't fully enforce the 32 chars limitation however but rather tries to be as
permissive as possible checking that any file path resulting for the upgrade
should be less than 256 chars (the windows limit).
PS: the first patch is the bulk of the change, the second one is the unit
tests. The later is huge because it renames the sstables in test/data to
include the keyspace name in them.
> 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
