[ https://issues.apache.org/jira/browse/CASSANDRA-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115485#comment-13115485 ]
Pavel Yaskevich commented on CASSANDRA-3231: -------------------------------------------- There is the question then - do we really need to change behavior of bytesToHex/hexToBytes methods of FBUtilities class? > CQL does not throw an error when invalid hex is supplied > -------------------------------------------------------- > > Key: CASSANDRA-3231 > URL: https://issues.apache.org/jira/browse/CASSANDRA-3231 > Project: Cassandra > Issue Type: Bug > Components: Core > Affects Versions: 0.8.5 > Reporter: Brandon Williams > Assignee: Pavel Yaskevich > Priority: Minor > Fix For: 0.8.7 > > > As reported on irc, if you try to create an index on a CF with a default > comparator of BytesType, but you supply invalid hex, weird things happen. > Namely if you try to create one on 'category' you instead get one on > '\xca\xfe\xff\xff', which is 4 bytes that appears to coincide with attempting > to interpret 'ca', 'te', 'go', 'ry' as hex. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira