Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 25 Mar 2014 15:11:15 +0000 (UTC)
From: "Marcus Eriksson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12703437.1395748883737.1530.1395760275533@arcas>
In-Reply-To: <JIRA.12703437.1395748883737@arcas>
References: <JIRA.12703437.1395748883737@arcas>
Subject: [jira] [Commented] (CASSANDRA-6922) Investigate if we can drop
 ByteOrderedPartitioner and OrderPreservingPartitioner in 3.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Marcus Eriksson commented on CASSANDRA-6922:
--------------------------------------------

Biggest benefit is that we avoid having code around that we don't think anyone should use.

Not a big deal, but reducing the amount of configuration choices for operators is a good thing.

> 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)