[
https://issues.apache.org/jira/browse/CASSANDRA-10179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14713417#comment-14713417
]
Sylvain Lebresne commented on CASSANDRA-10179:
----------------------------------------------
I'm not sure what [~beobal] has in mind exactly when he said " both the python
and java drivers make assumptions about what an AlreadyExistsException means",
but I would said it's not the driver the problem truly, it's that clients will
presumably be checking for {{InvalidQueryException}} in this case, and changing
the exception will break that code. It's not a problem it's used for MV in that
case since that's a new feature.
> 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)
