[
https://issues.apache.org/jira/browse/CASSANDRA-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-1205.
---------------------------------------
Resolution: Later
Ordered(anything not bytes) is a super niche feature since that says your
entire cluster has that key type. The main type that would be reasonable for
would be strings, which happen to compare well as bytes anyway.
> Unify Partitioners and AbstractTypes
> ------------------------------------
>
> Key: CASSANDRA-1205
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1205
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Stu Hood
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
