Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 50BE8183EE for ; Thu, 17 Mar 2016 09:17:34 +0000 (UTC) Received: (qmail 24829 invoked by uid 500); 17 Mar 2016 09:17:34 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 24764 invoked by uid 500); 17 Mar 2016 09:17:34 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 24686 invoked by uid 99); 17 Mar 2016 09:17:33 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Mar 2016 09:17:33 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id A87F52C1F68 for ; Thu, 17 Mar 2016 09:17:33 +0000 (UTC) Date: Thu, 17 Mar 2016 09:17:33 +0000 (UTC) From: "Sylvain Lebresne (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-11255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15199190#comment-15199190 ] Sylvain Lebresne commented on CASSANDRA-11255: ---------------------------------------------- The only thing I'm wondering is if for consistency we shouldn't have a {{floatprecision}} for COPY, even if it default to the cqlsh option. Otherwise, it's weird when you want to change both precision to have to use the cqlsh option for float and the COPY one for double. Also, wouldn't it make sense to add a {{double_precision}} option to cqlsh for consistency? > 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)