[ https://issues.apache.org/jira/browse/CASSANDRA-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
paul cannon reopened CASSANDRA-3149: ------------------------------------ So, this apparently didn't go far enough: the CQL parser still thinks "date" is an ok type, and "timestamp" isn't. If you try to execute this with CQL in any cassandra after this change: {noformat} CREATE COLUMNFAMILY foo ( KEY timestamp PRIMARY KEY ); {noformat} ..or use {{timestamp}} anywhere else a validator type is expected, you'll get an IRE with "{{no viable alternative at input 'timestamp'}}". src/java/org/apache/cassandra/cql/Cql.g needs to have "date" changed to "timestamp". It looks like all the other types line up right. > Update CQL type names to match expected (SQL) behavor > ----------------------------------------------------- > > Key: CASSANDRA-3149 > URL: https://issues.apache.org/jira/browse/CASSANDRA-3149 > Project: Cassandra > Issue Type: Improvement > Affects Versions: 0.8.0 > Reporter: Jonathan Ellis > Assignee: Jonathan Ellis > Priority: Minor > Labels: cql > Fix For: 1.0.0 > > Attachments: 3149.txt > > > As discussed in CASSANDRA-3031, we should make the following changes: > - rename bytea to blob > - rename date to timestamp > - remove int, pending addition of CASSANDRA-3031 (bigint and varint will be > unchanged) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira