In cqlsh, timestamp is escaped with double quotes as for reserved keywords when according to the cql documentation it is not a reserved keyword.
clqsh relies on metadata.maybe_escape_name() to decide whether to escape keywords.
To reproduce the problem, in cqlsh create the following table:
This will lead to the following completion when building an insert statement:
You may want to review other keywords as well.
Please see CASSANDRA-9232 for more details.
Missing a couple unreserved keywords? Otherwise, +1.
Based on changes only unit tests were needed. +1 LGTM.