Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 6 Apr 2011 00:59:05 +0000 (UTC)
From: "Ryan King (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <769503326.36642.1302051545921.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CASSANDRA-1205) Unify Partitioners and
 AbstractTypes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan King updated CASSANDRA-1205:
---------------------------------

    Fix Version/s:     (was: 0.8)
                   1.0

> Unify Partitioners and AbstractTypes
> ------------------------------------
>
>                 Key: CASSANDRA-1205
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1205
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Stu Hood
>            Priority: Critical
>             Fix For: 1.0
>
>
> There is no good reason for Partitioners to have different semantics than AbstractTypes. Instead, we should probably have 2 partitioners: Random and Ordered, where the Ordered partitioner requires an AbstractType to be specified, defaulting to BytesType.
> One solution [suggested by jbellis|https://issues.apache.org/jira/browse/CASSANDRA-767?focusedCommentId=12841565&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12841565] is to have AbstractType generate a collation id (essentially, a Token) for a set of bytes.
> Looking forward, we should probably consider laying the groundwork to add native support for compound row keys here as well.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira