Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <678355616.1245207967548.JavaMail.jira@brutus>
Date: Tue, 16 Jun 2009 20:06:07 -0700 (PDT)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Commented: (CASSANDRA-79) Multi-table support
In-Reply-To: <1843494641.1239636674836.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720480#action_12720480 ] 

Jonathan Ellis commented on CASSANDRA-79:
-----------------------------------------

There is a little more to do but this will do for a start I think.

The remaining parts are (1) move the system columnfamilies into their own Table (they are initialized in DatabaseDescriptor.storeMetadata) and (2) testing.  I added a note to http://wiki.apache.org/cassandra/HowToContribute linking the Hudson coverage reports and explaining how to build one manually.  Potential problem areas for this ticket are the CommitLog classes and (once we migrate them) the code dealing with system tables, particularly Hints. 

> 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, 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, 0006-cleanup-of-table.open.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.