Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 24 Aug 2015 13:36:46 +0000 (UTC)
From: "Sylvain Lebresne (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12849083.1437821867000.145897.1440423406023@Atlassian.JIRA>
In-Reply-To: <JIRA.12849083.1437821867000@Atlassian.JIRA>
References: <JIRA.12849083.1437821867000@Atlassian.JIRA>
 <JIRA.12849083.1437821867246@arcas>
Subject: [jira] [Updated] (CASSANDRA-9901) Make
 AbstractType.isByteOrderComparable abstract
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-9901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sylvain Lebresne updated CASSANDRA-9901:
----------------------------------------
    Reviewer: Sylvain Lebresne  (was: Robert Stupp)

> Make AbstractType.isByteOrderComparable abstract
> ------------------------------------------------
>
>                 Key: CASSANDRA-9901
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9901
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Benedict
>            Assignee: Benedict
>             Fix For: 3.0 beta 2
>
>
> I can't recall _precisely_ what was agreed at the NGCC, but I'm reasonably sure we agreed to make this method abstract, put some javadoc explaining we may require fields to yield true in the near future, and potentially log a warning on startup if a user-defined type returns false.
> This should make it into 3.0, IMO, so that we can look into migrating to byte-order comparable types in the post-3.0 world.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)