Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 4 Jun 2015 18:11:40 +0000 (UTC)
From: "Robert Stupp (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12835475.1433440610000.13911.1433441500361@Atlassian.JIRA>
In-Reply-To: <JIRA.12835475.1433440610000@Atlassian.JIRA>
References: <JIRA.12835475.1433440610000@Atlassian.JIRA>
 <JIRA.12835475.1433440610213@arcas>
Subject: [jira] [Commented] (CASSANDRA-9550) Support fixed precision data
 type
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Robert Stupp commented on CASSANDRA-9550:
-----------------------------------------

Can't {{BigDecimal}} maths solve that?

> Support fixed precision data type
> ---------------------------------
>
>                 Key: CASSANDRA-9550
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9550
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter:  Brian Hess
>
> SQL databases support a fixed precision data type.  When converting data models from SQL DBs to Cassandra, the choices are not clear.  DOUBLE or FLOAT are possibilities, but with UDFs and Aggregates this is actually a lot less clear, as you really do need fixed precision arithmetic.  That is, one flaw with floating-point math is that the order of the operations can change the final result.  That is not an issue with fixed precision arithmetic (though other trade-offs are there).


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