Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 25 Jun 2013 05:48:20 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12654635.1372121988641.169948.1372139300386@arcas>
In-Reply-To: <JIRA.12654635.1372121988641@arcas>
References: <JIRA.12654635.1372121988641@arcas>
Subject: [jira] [Updated] (CASSANDRA-5697) Semi-colons not Allowed in CQL3
 Batch Statements
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-5697:
--------------------------------------

             Priority: Minor  (was: Major)
    Affects Version/s:     (was: 1.2.5)
                       1.2.0
             Assignee: Aleksey Yeschenko

The grammar suggests that it was intended for semicolon to be optional.  I guess some kind of antlr nondeterminism makes it not work as designed?
                
> Semi-colons not Allowed in CQL3 Batch Statements
> ------------------------------------------------
>
>                 Key: CASSANDRA-5697
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5697
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 1.2.0
>         Environment: Mac OSX, cqlsh 3.0.2
>            Reporter: Russell Alexander Spitzer
>            Assignee: Aleksey Yeschenko
>            Priority: Minor
>              Labels: cql
>
> The documentation for BATCH statements declares that semicolons are required between update operations. Currently including them results in an error 'expecting K_APPLY'. To match the design specifications, semi-colons should be allowed or optional. 

--
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