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

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2009/05/19 05:18:45 UTC

[jira] Created: (CASSANDRA-187) per-CF key collation

per-CF key collation
--------------------

                 Key: CASSANDRA-187
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-187
             Project: Cassandra
          Issue Type: New Feature
            Reporter: Jonathan Ellis


collation is not necessarily one-size-fits-all.

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

[jira] Resolved: (CASSANDRA-187) per-CF key collation

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.

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

Jonathan Ellis resolved CASSANDRA-187.
--------------------------------------

    Resolution: Won't Fix

this implies having one token per node per CF, since the key/token comparators would no longer be one-size-fits all.  bad idea.

> per-CF key collation
> --------------------
>
>                 Key: CASSANDRA-187
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-187
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>
> collation is not necessarily one-size-fits-all.

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