[
https://issues.apache.org/jira/browse/CASSANDRA-11331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188963#comment-15188963
]
Sylvain Lebresne commented on CASSANDRA-11331:
----------------------------------------------
bq. we can broaden the scope of the IF NOT EXISTS check to include duplicates
in all but name
I think we should. And honestly, from a user point of view, this sounds a lot
like a regression and it's hard to argue it's not.
> Create Index IF NOT EXISTS throws error when index already exists
> -----------------------------------------------------------------
>
> Key: CASSANDRA-11331
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11331
> Project: Cassandra
> Issue Type: Bug
> Components: CQL
> Reporter: Philip Thompson
> Assignee: Sam Tunnicliffe
> Fix For: 3.0.x, 3.x
>
>
> While testing with trunk, I see that issuing the following queries throws an
> InvalidRequest, despite being valid.
> {code}
> CREATE KEYSPACE k WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': '1'} AND durable_writes = true;
> USE k;
> CREATE TABLE k.t (
> id int PRIMARY KEY,
> v int,
> v2 int,
> v3 text
> );
> CREATE INDEX IF NOT EXISTS ON t (v2);
> CREATE INDEX IF NOT EXISTS ON t (v2);
> InvalidRequest: code=2200 [Invalid query] message="Index t_v2_idx_1 is a
> duplicate of existing index t_v2_idx"
> {code}
> The second {{CREATE INDEX IF NOT EXISTS}} should work fine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
