[
https://issues.apache.org/jira/browse/CASSANDRA-10179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14713441#comment-14713441
]
Sylvain Lebresne commented on CASSANDRA-10179:
----------------------------------------------
Right, there is that too. Anyway, I think that boils down to the fact that if
we do do this change, it needs to be protocol 4 only and we need the proper
modifications to the protocol so drivers can distinguish between a table and
index creation.
> Duplicate index should throw AlreadyExistsException
> ---------------------------------------------------
>
> Key: CASSANDRA-10179
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10179
> Project: Cassandra
> Issue Type: Bug
> Reporter: T Jake Luciani
> Assignee: Sam Tunnicliffe
> Priority: Minor
> Fix For: 3.0.x
>
>
> If a 2i already exists we currently throw a InvalidQueryException. This
> should be a AlreadyExistsException for consistency like trying to create the
> same CQL Table twice.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
