cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7225) < is <= and > is >= in CQL
Date Fri, 16 May 2014 11:23:12 GMT


Sylvain Lebresne commented on CASSANDRA-7225:

That "Note" section is definitively wrong and refers to CQL2. But looking at it, the whole
help section (the ... part in the excerpt above) is actually wrong: it refers to {{KEY}} and
other "key filter" which are CQL2 things, it says terms can appear on both side of the operator
which is wrong and overall use the wrong vocabulary. And that's not the only section to be
outdated, in fact the vast majority of topics seems to be refering to CQL2 rather than CQL3
(create_table_types refers to {{KEY}}, create_index says the column name don't have to exist
which is incorrect, create_table_options don't reference COMPACT STORAGE or CLUSTERING ORDER,
updates of collection are not documented) and the vocabulary/presentation is overall a bit
dated (may references to "key values" which is more of a CQL2 notion, clustering columns should
be discussed much more prominently in create_table, etc...). Overall, the help seems to try
to save duplication by having topic common to CQL2 and CQL3 but in many case it ends up being
wrong and confusing for CQL3. Since CQL3 is the one that is there to stay, we should make
sure the help for CQL3 is consistent and up to date (if this means that the CQL2 is less good,
that's less of a problem imo).

As a side note, maybe clqsh help topics could keep the amount of details low and link to the
[online help|] for details.

Anyway, making this ticket a "fix/modernize cqlsh help" to fix all that.

> < is <= and > is >= in CQL
> --------------------------
>                 Key: CASSANDRA-7225
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Robert Stupp
>            Priority: Trivial
>              Labels: cqlsh
> Just a small line of text in cqlsh "help" command indicates that < is <= and >
is >= in CQL.
> This is confusing to many people (including me :) ) because I did not expect < to
return the "equals" portion.
> Please allow distinct behaviours for <, <=, > and >= in CQL queries. Maybe
in combination with CASSANDRA-5184 and/or CASSANDRA-4914 

This message was sent by Atlassian JIRA

View raw message