cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (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 22:17:54 GMT

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

Jason Brown commented on CASSANDRA-6922:
----------------------------------------

bq. Curious what the legitimate use cases are ...

A long time ago, and I'm not remembering so well, there was a project back at netflix where
the users wanted to map a set of their middle-ware services to an explicit range of the database.
They wanted to be able to read the entire range into their app's memory for metrics calculation
and such. Also, as per [~xedin]'s earlier comment, it looks like Titan makes use of BOP. I
wonder if this is still true? Poking at the current github code for Titan, I do see some some
references to BOP, but not sure if it's legacy or still used or ....


> 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