[
https://issues.apache.org/jira/browse/CASSANDRA-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-3.
------------------------------------
Resolution: Duplicate
This was resubmitted in pieces for review, culminating in CASSANDRA-71.
> 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
> Assignee: 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.
