[
https://issues.apache.org/jira/browse/CASSANDRA-9224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tyler Hobbs updated CASSANDRA-9224:
-----------------------------------
Attachment: 9224-2.1.txt
> Figure out a better default float precision rule for cqlsh
> ----------------------------------------------------------
>
> Key: CASSANDRA-9224
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9224
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Tyler Hobbs
> Assignee: Stefania
> Labels: cqlsh
> Fix For: 3.x, 2.1.x, 2.2.x
>
> Attachments: 9224-2.1.txt
>
>
> We currently use a {{DEFAULT_FLOAT_PRECISION}} of 5 in cqlsh with formatting
> {{'%.*g' % (float_precision, val)}}. In practice, this is way too low. For
> example, 12345.5 will show up as 123456. Since the float precision is used
> for cqlsh's COPY TO, it's particularly important that we maintain as much
> precision as is practical by default.
> There are some other tricky considerations, though. If the precision is too
> high, python will do something like this:
> {noformat}
> > '%.25g' % (12345.5555555555555555,)
> '12345.55555555555474711582'
> {noformat}
> That's not terrible, but it would be nice to avoid if we can.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
