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

Stefania commented on CASSANDRA-11474:
--------------------------------------

Patches and CI available here:

||2.2||3.0||trunk||
|[patch|https://github.com/stef1927/cassandra/commits/11474-2.2]|[patch|https://github.com/stef1927/cassandra/commits/11474-3.0]|[patch|https://github.com/stef1927/cassandra/commits/11474]|
|[dtest|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-11474-2.2-dtest/]|[dtest|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-11474-3.0-dtest/]|[dtest|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-11474-dtest/]|

There is a conflict from 2.2 to 3.0 whilst the 3.0 patch merges cleanly into 
trunk.

I should also note that this is a pretty serious limitation of COPY FROM, 
albeit very unlikely to occur. However, we don't need the fix in 2.1 because 
{{batch_size_fail_threshold_in_kb}} is only available in 2.2+.

Additional dtest to reproduce the problem are available 
[here|https://github.com/stef1927/cassandra-dtest/tree/11474].

> cqlsh: COPY FROM should use regular inserts for single statement batches
> ------------------------------------------------------------------------
>
>                 Key: CASSANDRA-11474
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11474
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>            Reporter: Stefania
>            Assignee: Stefania
>              Labels: lhf
>             Fix For: 2.2.x, 3.0.x, 3.x
>
>
> I haven't reproduced it with a test yet but, from code inspection, if CQL 
> rows are larger than {{batch_size_fail_threshold_in_kb}} and this parameter 
> cannot be changed, then data import will fail.
> Users can control the batch size by setting MAXBATCHSIZE.
> If a batch contains a single statement, there is no need to use a batch and 
> we should use normal inserts instead or, alternatively, we should skip the 
> batch size check for unlogged batches with only one statement.



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

Reply via email to