[
https://issues.apache.org/jira/browse/CASSANDRA-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989213#comment-12989213
]
Robbie Strickland commented on CASSANDRA-2079:
----------------------------------------------
I was/am using C#, no high-level client. I'm doing a big endian conversion on
an integer being used as a supercolumn name. Previously (in 0.6.x) I would get
errors trying to use the LongType comparator because of size issues, which is
why I used AsciiType (same effect without the size validation). The
IntegerType comparator gives me what I was looking for in 0.6.x, but I lost a
few days trying to figure out what was generating errors (I'm using AsciiType
all over the place, so it wasn't immediately apparent where the root was).
I understand and agree with the more robust validation and addition of the
IntegerType, but the comment that I should just send valid data is really not
accurate since I was using the only available workaround at the time. For the
benefit of others who are migrating and may have run into this issue, I think
adding something in the documentation regarding the stricter validation
(outside an obscure JIRA issue) would be helpful. In fact a comprehensive
migration doc would really be great since 0.7 made some fundamental changes.
> 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
