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 Ellis (JIRA)" <ji...@apache.org> on 2013/09/20 23:34:53 UTC

[jira] [Resolved] (CASSANDRA-3889) malformed UPDATE queries causing NumberFormatException, AssertionError

     [ https://issues.apache.org/jira/browse/CASSANDRA-3889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-3889.
---------------------------------------

    Resolution: Won't Fix
    
> malformed UPDATE queries causing NumberFormatException, AssertionError
> ----------------------------------------------------------------------
>
>                 Key: CASSANDRA-3889
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3889
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.0
>         Environment: Cassandra 1.1
>            Reporter: paul cannon
>            Priority: Minor
>              Labels: cql
>
> Given a columnfamily like:
> {code}
>         CREATE TABLE CounterCF (KEY text PRIMARY KEY, count_me counter)
>             WITH comparator = ascii AND default_validation = counter;
> {code}
> This query causes Cassandra to throw a NumberFormatException and close the thrift connection (yes, it's not valid, cause it's a counter CF)
> {code}
> UPDATE CounterCF SET count_me = count_me + 2, x = 'a' WHERE key = 'counter1';
> {code}
> And this variant causes an AssertionError and a permanently unresponsive thrift connection:
> {code}
> update CounterCF set count_me=count_me+2, x='' where key = 'counter1';
> {code}
> When a valid hex string (with a multiple of 2 hex digits) is used instead of 'a' or '', then the expected InvalidRequestException is seen.
> This is related to CASSANDRA-2851, but seems unimportant and incidental enough that a new ticket is more appropriate than reopening that one.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira