cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6922) Investigate if we can drop ByteOrderedPartitioner and OrderPreservingPartitioner in 3.0
Date Mon, 23 Mar 2015 10:43:12 GMT

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

Benedict commented on CASSANDRA-6922:
-------------------------------------

New storage formats would also be materially simplified if we can assume a hash distribution
of data. For locality there has been talk (not sure if a ticket has been filed) of supporting
token computation against only a prefix of the partition key, which would support most use
cases. The problem we have with maintaining both is that they are pretty (by definition) orthogonal
approaches, and so we make a lot of decisions in favour of hashed at the expense of BOP, but
it lingering still creates a number of headaches and less optimal decisions. I'm +1 deprecating,
and slating for removal.

> 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.3.4#6332)

Mime
View raw message