Sam Tunnicliffe created CASSANDRA-8760:
------------------------------------------
Summary: CQL inconsistencies with CREATE ROLE options
Key: CASSANDRA-8760
URL: https://issues.apache.org/jira/browse/CASSANDRA-8760
Project: Cassandra
Issue Type: Bug
Reporter: Sam Tunnicliffe
Assignee: Sam Tunnicliffe
Priority: Trivial
Fix For: 3.0
Most CQL statements which support options with values require an '=' between
the option name & value.
{code}
CREATE KEYSPACE ks WITH replication = {'class': 'SimpleStrategy',
'replication_factor': 1};
CREATE TABLE ks.cf (k int PRIMARY KEY, v int) WITH default_time_to_live = 3600;
CREATE INDEX ON ks.cf(v) USING SomeCustomIndexClass WITH prop1 = 'val1';
{code}
In contrast, CREATE & ALTER ROLE statements do not allow an '='.
{code}
CREATE ROLE foo WITH PASSWORD 'password';
CREATE ROLE bar WITH OPTIONS {'option1' : 1};
{code}
This isn't really a big problem, but it is inconsistent so it would be nice to
have CREATE/ALTER ROLE optionally support an equals sign before the PASSWORD
and OPTIONS opts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)