You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Stu Hood (JIRA)" <ji...@apache.org> on 2011/02/26 00:31:22 UTC

[jira] Updated: (CASSANDRA-1205) Unify Partitioners and AbstractTypes

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

Stu Hood updated CASSANDRA-1205:
--------------------------------

    Priority: Critical  (was: Major)

This has gotten a bit scary with the addition of LocalPartitioner: bumping priority.

> 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: 0.8
>
>
> 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