Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 25 Aug 2015 03:28:45 +0000 (UTC)
From: "Stefania (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12823511.1429814418000.154072.1440473325960@Atlassian.JIRA>
In-Reply-To: <JIRA.12823511.1429814418000@Atlassian.JIRA>
References: <JIRA.12823511.1429814418000@Atlassian.JIRA>
 <JIRA.12823511.1429814418004@arcas>
Subject: [jira] [Commented] (CASSANDRA-9232) "timestamp" is considered as a
 reserved keyword in cqlsh completion
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CASSANDRA-9232?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D=
14710519#comment-14710519 ]=20

Stefania commented on CASSANDRA-9232:
-------------------------------------

dtest pull request is [here|https://github.com/riptano/cassandra-dtest/pull=
/501].

CASSANDRA-9961 will take care of bundling the python driver once [PYTHON-37=
1|https://datastax-oss.atlassian.net/browse/PYTHON-371] is resolved, see co=
mment [here|https://issues.apache.org/jira/browse/CASSANDRA-9961?focusedCom=
mentId=3D14710518&page=3Dcom.atlassian.jira.plugin.system.issuetabpanels:co=
mment-tabpanel#comment-14710518], so I don't think we need to create a sepa=
rate ticket.

> "timestamp" is considered as a reserved keyword in cqlsh completion
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-9232
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9232
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Micha=C3=ABl Figui=C3=A8re
>            Assignee: Stefania
>            Priority: Trivial
>              Labels: cqlsh
>             Fix For: 3.x, 2.1.x
>
>
> cqlsh seems to treat "timestamp" as a reserved keyword when used as an id=
entifier:
> {code}
> cqlsh:ks1> create table t1 (int int primary key, ascii ascii, bigint bigi=
nt, blob blob, boolean boolean, date date, decimal decimal, double double, =
float float, inet inet, text text, time time, timestamp timestamp, timeuuid=
 timeuuid, uuid uuid, varchar varchar, varint varint);
> {code}
> Leads to the following completion when building an {{INSERT}} statement:
> {code}
> cqlsh:ks1> insert into t1 (int,=20
> "timestamp" ascii       bigint      blob        boolean     date        d=
ecimal     double      float       inet        text        time        time=
uuid    uuid        varchar     varint
> {code}
> "timestamp" is a keyword but not a reserved one and should therefore not =
be proposed as a quoted string. It looks like this error happens only for t=
imestamp. Not a big deal of course, but it might be worth reviewing the key=
words treated as reserved in cqlsh, especially with the many changes introd=
uced in 3.0.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)