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/07/16 23:52:15 UTC

[jira] Updated: (CASSANDRA-185) user-defined column ordering

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

Jonathan Ellis updated CASSANDRA-185:
-------------------------------------

    Attachment: 0004-r-m-tests-that-won-t-pass-until-we-do-303.txt
                0003-change-String-column-names-to-byte-to-allow-user-def.txt
                0002-r-m-time-sorted-columns.txt
                0001-CASSANDRA-185-introduce-column-compatibility-layer-t.txt

> user-defined column ordering
> ----------------------------
>
>                 Key: CASSANDRA-185
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-185
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>         Attachments: 0001-CASSANDRA-185-introduce-column-compatibility-layer-t.txt, 0002-r-m-time-sorted-columns.txt, 0003-change-String-column-names-to-byte-to-allow-user-def.txt, 0004-r-m-tests-that-won-t-pass-until-we-do-303.txt
>
>
> name ordering by ascii String order isn't general enough.
> we need to allow specifying a comparator class like we do (indirectly) for key ordering via the partitioner interface.
> per-CF would be best.

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