[
https://issues.apache.org/jira/browse/CASSANDRA-10277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14790989#comment-14790989
]
Benjamin Lerer commented on CASSANDRA-10277:
--------------------------------------------
* the unit test results for 2.2 are
[here|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-10277-2.2-testall/1/]
* the dtest results for 2.2 are
[here|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-10277-2.2-dtest/1/]
* the unit test results for 3.0 are
[here|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-10277-3.0-dtest/2/]
* the dtest results for 3.0 are
[here|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-10277-3.0-testall/2/]
+1
Thanks for patch
> Empty BATCH throws exception in Cassandra
> -----------------------------------------
>
> Key: CASSANDRA-10277
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10277
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Vovodroid
> Priority: Minor
> Fix For: 2.2.2
>
> Attachments: 10277.txt, emptybatch.patch, emptytest.patch
>
>
> Connect to Cassandra with cqlsh and perform empty BATCH statement:
> {code}BEGIN BATCH APPLY BATCH;{code}
> Following exception is thrown and logged
> {code}
> ERROR 14:02:07 Unexpected exception during request
> java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
> at java.util.ArrayList.rangeCheck(ArrayList.java:653) ~[na:1.8.0_45]
> at java.util.ArrayList.get(ArrayList.java:429) ~[na:1.8.0_45]
> at
> org.apache.cassandra.cql3.statements.BatchStatement$Parsed.prepare(BatchStatement.java:514)
> ~[main/:na]
> ...........................
> {code}
> It's caused because of access to batch statement list, even if it's empty.
> Proposed patch (for 2.2.0) is attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
