[
https://issues.apache.org/jira/browse/CASSANDRA-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13946776#comment-13946776
]
Sylvain Lebresne commented on CASSANDRA-6922:
---------------------------------------------
bq. it materially complicates new features like CASSANDRA-6696.
I haven't really followed this ticket, but what make OPP/BOPP particularly hard
to handle, compared to say RandomPartitioner? Because glancing at the patch, it
just look like code for M3P was just harcoded but I don't really see anything
specific that make it extremely hard to support OPP/BOPP. Just sound like we
need a new splitRanges() (but we need it for RandomPartitioner too and that
seems hardly to be the most complicated method ever).
> Investigate if we can drop ByteOrderedPartitioner and
> OrderPreservingPartitioner in 3.0
> ---------------------------------------------------------------------------------------
>
> Key: CASSANDRA-6922
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6922
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Marcus Eriksson
> Fix For: 3.0
>
>
> We would need to add deprecation warnings in 2.1, rewrite a lot of unit
> tests, and perhaps provide tools/guidelines to migrate an existing data set
> to Murmur3Partitioner.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
