cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-4185) Minor CQL3 fixes
Date Wed, 25 Apr 2012 14:12:17 GMT


Sylvain Lebresne updated CASSANDRA-4185:

    Attachment:     (was: 0004-Disallow-counters-for-PRIMARY-KEY-part.txt)
> Minor CQL3 fixes
> ----------------
>                 Key: CASSANDRA-4185
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 1.1.0
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>              Labels: cql3
>             Fix For: 1.1.1
>         Attachments: 0001-Fix-float-parsing.txt, 0002-Fix-compact-storage-validation.txt,
0003-Fix-COUNT-in-select.txt, 0004-Disallow-counters-for-PRIMARY-KEY-part-v2.txt
> The goal of this ticket is to be the home for a number of minor fixes/improvements in
CQL3 that I didn't felt warranted a ticket each. It includes 4 patches:
> * The first one fixes the grammar for float constants, so as to not recognize 3.-3, but
to actually allow 3. (i.e, with radix point but with the fractional part left blank)
> * The second one correctly detect the (invalid) case where a table is created with COMPACT
STORAGE but without any 'clustering keys'.
> * The third one fixes COUNT, first by making sure both COUNT(*) and COUNT(1) are correctly
recognized and also by "processing" the internal row before counting, are there isn't a 1-to-1
correspondence between internal rows and CQL rows in CQL3. The grammar change in this patch
actually rely on CASSANDRA-4184
> * The fourth and last patch disallows the counter type for keys (i.e. any column part
of the PRIMARY KEY) as it is completely non-sensical and will only led to confusion.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message