You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Greene (JIRA)" <ji...@apache.org> on 2009/08/12 03:12:18 UTC
[jira] Updated: (CASSANDRA-79) Multi-table support
[ https://issues.apache.org/jira/browse/CASSANDRA-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Greene updated CASSANDRA-79:
------------------------------------
Component/s: Core
> Multi-table support
> -------------------
>
> Key: CASSANDRA-79
> URL: https://issues.apache.org/jira/browse/CASSANDRA-79
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Critical
> Fix For: 0.4
>
> Attachments: 0001-CASSANDRA-79-goffinet-s-patch-modified-to-build-but.txt, 0002-fix-CF-table-dependencies-making-CommitLogTest-pass.txt, 0003-cleanup-of-table.open.txt, 0003-OptimizedImports-multitable-from-trunk-June-15-2009.patch, 0004-fix-id-generation-for-multiple-tables-and-rip-out-Tabl.txt, 0005-add-multitable-test.txt, 0006-remove-table_-from-CommitLog-with-test.txt, 0007-fix-more-null-table-parameters.patch
>
>
> Cassandra has preliminary support for multiple tables (namespaces / sets of ColumnFamilies) but a lot of the code assumes there is only one. Multitable support is important for allowing multiple applications to run on a single cluster. It's also useful to cleanly separate "system" columnfamilies from application data.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.