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

Sylvain Lebresne commented on CASSANDRA-4245:
---------------------------------------------

bq.  Where the case of the string is preserved but then ignored in queries.

I don't think that this is what the '6 columns' option does. Namely, if we have 
6 columns, it means that we don't ignore the case in queries (since we have 
multiple values for the same name but with different case). In other words, if 
its case insensitivity we want, it's the 3 columns option, for which I kind of 
agree with Jonathan and Brandon, can be done client side fairly easily by 
lower-casing everything. The 6 columns option is more about having a different 
string order that puts strings that differ only by case closer, which can be 
neat, but is it so useful that it justify being a native type?
                
> Provide a UT8Type (case insensitive) comparator
> -----------------------------------------------
>
>                 Key: CASSANDRA-4245
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4245
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Ertio Lew
>            Priority: Minor
>
> It is a common use case to use a bunch of entity names as column names & then 
> use the row as a search index, using search by range. For such use cases & 
> others, it is useful to have a UTF8 comparator that provides case insensitive 
> ordering of columns.

--
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

        

Reply via email to