[
https://issues.apache.org/jira/browse/CASSANDRA-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-79:
------------------------------------
Attachment: (was: 0001-Rebased-multitable-from-trunk-June-11-2009.patch)
> Multi-table support
> -------------------
>
> Key: CASSANDRA-79
> URL: https://issues.apache.org/jira/browse/CASSANDRA-79
> Project: Cassandra
> Issue Type: New Feature
> Affects Versions: trunk
> Reporter: Jonathan Ellis
> Priority: Critical
> Fix For: 0.4
>
> Attachments: 0001-CASSANDRA-79-add-CommitLog-test.txt,
> 0002-update-comments-perform-some-renames-r-m-unused-code.txt,
> 0003-OptimizedImports-multitable-from-trunk-June-15-2009.patch,
> 0003-switch-from-byte-to-BitSet-in-CommitLogHeader.txt,
> 0004-Chris-Goffinet-s-patch-with-minor-changes-to-get-it-to.txt,
> 0005-fix-CF-table-dependencies-making-CommitLogTest-pass.txt,
> 0006-cleanup-of-table.open.txt,
> 0007-fix-id-generation-for-multiple-tables-and-rip-out-Tabl.txt,
> 0008-add-multitable-test.txt
>
>
> 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.
