[
https://issues.apache.org/jira/browse/CASSANDRA-10179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14713436#comment-14713436
]
Sam Tunnicliffe commented on CASSANDRA-10179:
---------------------------------------------
What I meant was really more of a protocol issue than a driver one. The spec
says an AlreadyExists code will be followed by 2 strings representing a KS and
Table (the latter may be empty). The drivers also implement their own
exceptions accordingly, so for instance if {{CreateIndexStatement}} was simply
changed to {{AlreadyExistsException}}, the protocol wouldn't be able (yet) to
represent that it was an index that was the subject. So we'd need to update the
protocol to allow for additional information to be included and the drivers to
interpret that info.
> 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)
