Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 10 Nov 2014 16:07:57 +0000 (UTC)
From: "T Jake Luciani (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12735127.1408473608000.460594.1415635677105@Atlassian.JIRA>
In-Reply-To: <JIRA.12735127.1408473608000@Atlassian.JIRA>
References: <JIRA.12735127.1408473608000@Atlassian.JIRA>
 <JIRA.12735127.1408473608389@arcas>
Subject: [jira] [Updated] (CASSANDRA-7793) Utilize BATCH statements in COPY
 FROM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

T Jake Luciani updated CASSANDRA-7793:
--------------------------------------
    Fix Version/s:     (was: 2.1.2)
                   2.1.3

> Utilize BATCH statements in COPY FROM
> -------------------------------------
>
>                 Key: CASSANDRA-7793
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7793
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Mikhail Stepura
>            Priority: Minor
>              Labels: cqlsh
>             Fix For: 2.1.3
>
>
> If we assume that a significant subset of COPY FROM csv's are going to be results of COPY TO command, then rows will be grouped by the partition key. In that case we'd win from batching (until another partition key is met, and constrained by some limit of rows per batch, we don't want huge batches)


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