[ https://issues.apache.org/jira/browse/CASSANDRA-9232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Hanna updated CASSANDRA-9232: ------------------------------------ Component/s: (was: Materialized Views) > "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 > Components: Tools > Reporter: Michaël Figuière > Assignee: Stefania > Priority: Trivial > Labels: cqlsh > Fix For: 2.1.10, 2.2.1, 3.0 beta 2 > > > cqlsh seems to treat "timestamp" as a reserved keyword when used as an > identifier: > {code} > cqlsh:ks1> create table t1 (int int primary key, ascii ascii, bigint bigint, > 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, > "timestamp" ascii bigint blob boolean date > decimal double float inet text time > timeuuid 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 > timestamp. Not a big deal of course, but it might be worth reviewing the > keywords treated as reserved in cqlsh, especially with the many changes > introduced in 3.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org