You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by " Brian Hess (JIRA)" <ji...@apache.org> on 2015/08/06 04:52:05 UTC
[jira] [Issue Comment Deleted] (CASSANDRA-9302) Optimize cqlsh COPY
FROM, part 3
[ https://issues.apache.org/jira/browse/CASSANDRA-9302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Hess updated CASSANDRA-9302:
----------------------------------
Comment: was deleted
(was: There is also https://issues.apache.org/jira/browse/CASSANDRA-9048 That ticket has been tagged as "Later" for some reason, but the work continues at https://github.com/brianmhess/cassandra-loader
In addition to more options, the performance of cassandra-loader is 4x (or more) than COPY FROM in 2.1. Also, it is more stable and can handle wider rows (see https://issues.apache.org/jira/browse/CASSANDRA-9552))
> Optimize cqlsh COPY FROM, part 3
> --------------------------------
>
> Key: CASSANDRA-9302
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9302
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Jonathan Ellis
> Assignee: David Kua
> Fix For: 2.1.x
>
>
> We've had some discussion moving to Spark CSV import for bulk load in 3.x, but people need a good bulk load tool now. One option is to add a separate Java bulk load tool (CASSANDRA-9048), but if we can match that performance from cqlsh I would prefer to leave COPY FROM as the preferred option to which we point people, rather than adding more tools that need to be supported indefinitely.
> Previous work on COPY FROM optimization was done in CASSANDRA-7405 and CASSANDRA-8225.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)