Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 18 Mar 2016 08:02:33 +0000 (UTC)
From: "Stefania (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12944756.1456456969000.57515.1458288153498@Atlassian.JIRA>
In-Reply-To: <JIRA.12944756.1456456969000@Atlassian.JIRA>
References: <JIRA.12944756.1456456969000@Atlassian.JIRA>
 <JIRA.12944756.1456456969093@arcas>
Subject: [jira] [Commented] (CASSANDRA-11255) COPY TO should have higher
 double precision
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Stefania commented on CASSANDRA-11255:
--------------------------------------

I've separated the COPY default option values from the cqlsh default values, and restarted CI.

When committing, we need to merge the [pull request|https://github.com/riptano/cassandra-dtest/pull/865] as well.

> COPY TO should have higher double precision
> -------------------------------------------
>
>                 Key: CASSANDRA-11255
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11255
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Stefania
>            Assignee: Stefania
>              Labels: doc-impacting, lhf
>             Fix For: 3.x
>
>
> At the moment COPY TO uses the same float precision as cqlsh, which by default is 5 but it can be changed in cqlshrc. However, typically people want to preserve precision when exporting data and so this default is too low for COPY TO.
> I suggest adding a new COPY FROM option to specify floating point precision with a much higher default value, for example 12.


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