Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <451515837.1245760568005.JavaMail.jira@brutus>
Date: Tue, 23 Jun 2009 05:36:08 -0700 (PDT)
From: "Hudson (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Commented: (CASSANDRA-188) raise error if supercolumn is
 configured as time-sorted
In-Reply-To: <442121195.1242749805673.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-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723056#action_12723056 ] 

Hudson commented on CASSANDRA-188:
----------------------------------

Integrated in Cassandra #117 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/117/])
    multitable support.

fix CF table dependencies, making CommitLogTest pass.  Also fixes  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 CASSANDRA-79


> raise error if supercolumn is configured as time-sorted
> -------------------------------------------------------
>
>                 Key: CASSANDRA-188
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-188
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.4
>
>
> then we don't have to silently "fix" it by doing stuff like
> if("Super".equals(columnType) || DatabaseDescriptor.isNameSortingEnabled(cfName))

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.