[jira] Commented: (CASSANDRA-2079) AsciiType comparator no longer usable on numeric types in 0.7

["Aaron Morton (JIRA)" <ji...@apache.org>]

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

Aaron Morton commented on CASSANDRA-2079:
-----------------------------------------

The AsciiType is checking that the bytes are in the range of 0 to 127, previously validation was done by just by checking the value could be turned into a string. see CASSANDRA-1814 Any values outside the range of US_ASCII would have been replaced http://download.oracle.com/javase/6/docs/api/java/lang/String.html#String(byte[], int, int, java.nio.charset.Charset)

What client were you using? Were integers stored as strings or binary values? 

Anyone, is there a wider issue here with the change to the validation in CASSANDRA-1814 catching people out?

> AsciiType comparator no longer usable on numeric types in 0.7
> -------------------------------------------------------------
>
>                 Key: CASSANDRA-2079
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2079
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Documentation & website
>    Affects Versions: 0.7.0
>         Environment: Ubuntu 10
>            Reporter: Robbie Strickland
>             Fix For: 0.7.0
>
>
> Prior to 0.7, if you wanted to use integer values other than long types as column names, you had to use AsciiType to get a valid numeric-order comparison.  If you migrate to 0.7 you need to change the comparison type to "IntegerType", otherwise you will get the following error: InvalidRequestException(Why: Invalid byte for ascii: -51), or something similar.  The documentation should be updated to warn users of this issue.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira