cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-79) Multi-table support
Date Wed, 17 Jun 2009 03:12:07 GMT


Jonathan Ellis commented on CASSANDRA-79:

I see a bug already. :)

As I mentioned (way) above, we want to have Row serialize the table name into the commitlog.
 CommitLog shouldn't have a table_ variable; it will contain rows from lots of tables.

Creating a test that breaks this will need to force the log replay code to run.  Haven't looked
to see how hard that is.

> Multi-table support
> -------------------
>                 Key: CASSANDRA-79
>                 URL:
>             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, 0001-Rebased-multitable-from-trunk-June-11-2009.patch,
0002-OptimizedImports-multitable-from-trunk-June-15-2009.patch, 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,, 0007-fix-id-generation-for-multiple-tables-and-rip-out-Tabl.txt,
0008-add-multitable-test.txt, multitable_v1.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.

View raw message