[jira] [Commented] (CASSANDRA-7654) CQL INSERT improvement

["Jack Krupansky (JIRA)" <ji...@apache.org>]

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

Jack Krupansky commented on CASSANDRA-7654:
-------------------------------------------

1. For doc purposes, what is the rationale for restricting the insert to a single partition?

2. Will subsequent inserts occur if any of the inserts fail due to consistency or for any other reason?

3. Can the app assume that the inserts will be attempted in parallel?

4. Will the driver route the insert to the insert a node that owns that partition key?

4a. Should all of the inserts really be routed to the same node, or distributed according to RF? (Driver question.)

5. Is it also proposed to enhance the driver to support such a "batch" insertion of documents?
 

> CQL INSERT improvement
> ----------------------
>
>                 Key: CASSANDRA-7654
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7654
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Robert Stupp
>
> It would be nice to be able to add multiple rows using a single {{INSERT}}.
> Restricted to the same partition.
> For example:
> Current behaviour:
> {noformat}
> INSERT INTO comp_key (key, num_val)
>   VALUES ('foo', 1, 41);
> INSERT INTO comp_key (key, num_val)
>   VALUES ('foo', 2, 42);
> {noformat}
> Wanted behaviour:
> {noformat}
> INSERT INTO comp_key (key, num_val)
>   VALUES
>     ('foo', 1, 41),
>     ('foo', 2, 42),
>     ('foo', 3, 42),
>     ('foo', 4, 42);
> {noformat}
> Assumed table def:
> {noformat}
> CREATE TABLE comp_key (
>   key     TEXT,
>   clust   INT,
>   num_val DECIMAL,
>   PRIMARY KEY ( key, clust )
> );
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)