[ https://issues.apache.org/jira/browse/CASSANDRA-12733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joshua McKenzie updated CASSANDRA-12733: ---------------------------------------- Assignee: Alex Petrov (was: Jeremiah Jordan) > 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: Alex Petrov > Priority: Minor > > 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)