You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jun Rao (JIRA)" <ji...@apache.org> on 2009/03/25 19:17:50 UTC
[jira] Commented: (CASSANDRA-3) Allow non-hash-based partitioning
schemes to allow truly order-preserving storage
[ https://issues.apache.org/jira/browse/CASSANDRA-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689182#action_12689182 ]
Jun Rao commented on CASSANDRA-3:
---------------------------------
Jonathan,
Do you imagine that one can implement some sort of range partitioning using your patch? The thing with range partitioning is that the partitioner has to keep some states. I am not sure how to enforce the partitioners on different nodes to maintain the same states. Do you require the patitioner to be stateless?
> Allow non-hash-based partitioning schemes to allow truly order-preserving storage
> ---------------------------------------------------------------------------------
>
> Key: CASSANDRA-3
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Jonathan Ellis
> Attachments: partition-1.patch, partition-2.patch, partition-3.patch, partition-4.patch, partition-5.patch, partition-6.patch
>
>
> An order-preserving hash has too many limitations to be useful in production where key lengths tend to have low variance. We need to make Cassandra more flexible and define a partitioner as responsible for String -> EndPoint instead of String -> BigInteger.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.