Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 10 Sep 2013 13:27:51 +0000 (UTC)
From: "Sylvain Lebresne (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12667806.1378819566330.107793.1378819671570@arcas>
In-Reply-To: <JIRA.12667806.1378819566330@arcas>
References: <JIRA.12667806.1378819566330@arcas>
Subject: [jira] [Created] (CASSANDRA-5994) Allow empty CQL3 batches (as
 no-op)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Sylvain Lebresne created CASSANDRA-5994:
-------------------------------------------

             Summary: Allow empty CQL3 batches (as no-op)
                 Key: CASSANDRA-5994
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5994
             Project: Cassandra
          Issue Type: Improvement
            Reporter: Sylvain Lebresne
            Assignee: Sylvain Lebresne
            Priority: Trivial
             Fix For: 1.2.10
         Attachments: 5994.txt

The CQL3 parser doesn't allow empty batch statements and bitches with a parsing error. While clients should probably make sure they don't generate empty batches as it's useless, it's easy for client that general batch requests to forget handling the empty case, ending up sending an empty batch. it's a tad annoying to get a runtime error in production just for that. Let just it being a no-op.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira