[
https://issues.apache.org/jira/browse/CASSANDRA-12733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15565421#comment-15565421
]
Aleksey Yeschenko commented on CASSANDRA-12733:
-----------------------------------------------
Committed as
[c7fb95c98d2c370fcdb8e0389528ce6668f3a58c|https://github.com/apache/cassandra/commit/c7fb95c98d2c370fcdb8e0389528ce6668f3a58c]
to 3.X and merged into trunk. For the record, I still find the ticket silly,
but ¯\_(ツ)_/¯
> Throw an exception if there is a prepared statement id hash conflict.
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-12733
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12733
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL
> Reporter: Jeremiah Jordan
> Assignee: Jeremiah Jordan
> Priority: Minor
> Fix For: 3.10
>
>
> I seriously doubt there is any chance of actually getting two prepared
> statement strings that have the same MD5. But there should probably be
> checks in QueryProcessor.getStoredPreparedStatement that the query string of
> the statement being prepared matches the query string of the ID returned from
> the cache when one already exists there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
