[
https://issues.apache.org/jira/browse/CASSANDRA-11474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15242254#comment-15242254
]
Stefania commented on CASSANDRA-11474:
--------------------------------------
Thanks for the review.
I've removed the single insert special case from the patch on trunk but left
the fix on reporting errors during the initialization phase of worker
processes. I've also prepared the ticket for commit by editing CHANGES.txt and
the commit messages, please check if the description seems reasonable.
I've restarted CI, results are still pending.
Also, here is the dtest [pull
request|https://github.com/riptano/cassandra-dtest/pull/928].
> 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
> Priority: Minor
> 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)
