cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandeep Tata (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-185) user-defined column ordering
Date Mon, 20 Jul 2009 22:17:14 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733378#action_12733378
] 

Sandeep Tata commented on CASSANDRA-185:
----------------------------------------

Ah .. just noticed the happy side-effect that EfficientBidiMap is now replaced by a single
ConcurrentSkipListMap ...

> 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.


Mime
View raw message