[
https://issues.apache.org/jira/browse/CASSANDRA-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723058#action_12723058
]
Hudson commented on CASSANDRA-79:
---------------------------------
Integrated in Cassandra #117 (See
[http://hudson.zones.apache.org/hudson/job/Cassandra/117/])
fix more null table parameters.
patch by jbellis; reviewed by goffinet for
remove table_ from CommitLog and add multitable tests.
patch by jbellis; reviewed by goffinet for
fix columnfamily id generation in the face of multiple tables and rip out
TableMetadata serialization, which only complicates things needlessly.
patch by jbellis; reviewed by goffinet for
cleanup of table.open.
patch by jbellis; reviewed by goffinet for
multitable support.
fix CF table dependencies, making CommitLogTest pass. Also fixes CASSANDRA-188
in passing.
fix tablename being null bugs by always parsing tablename from filename.
fix last part of SequenceFile.
patch by jbellis; reviewed by goffinet for
Pass and write table parameter as needed throughout the codebase to add
multitable support.
(Many places cheated and just assumed that tables.get(0) was the only table.)
Patch builds but does not yet pass tests.
Patch by goffinet; reviewed by jbellis for
> Multi-table support
> -------------------
>
> Key: CASSANDRA-79
> URL: https://issues.apache.org/jira/browse/CASSANDRA-79
> Project: Cassandra
> Issue Type: New Feature
> 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.
