You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Shook (JIRA)" <ji...@apache.org> on 2015/02/26 23:26:06 UTC

[jira] [Commented] (CASSANDRA-8869) Normalize prepared query text

    [ https://issues.apache.org/jira/browse/CASSANDRA-8869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14339310#comment-14339310 ] 

Jonathan Shook commented on CASSANDRA-8869:
-------------------------------------------

We looked at this in more detail. It initially looked like a trivial change, but after digging in a bit, there are some potentially thorny issues how it might behave in practice.

For example, if you are using 75% of the allotted space for prepared statement caching, then it would be possible to seriously impact a production load due to a rolling upgrade churning the cache.

Fixing this issue might not be worth the risk or even the trouble to log a warning.

> Normalize prepared query text
> -----------------------------
>
>                 Key: CASSANDRA-8869
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8869
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API
>            Reporter: Michael Penick
>            Priority: Trivial
>              Labels: lhf
>
> It's possible for equivalent queries with different case and/or whitespace to resolve to different prepared statement hashes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)