[
https://issues.apache.org/jira/browse/CASSANDRA-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277721#comment-13277721
]
Aaron Morton commented on CASSANDRA-4245:
-----------------------------------------
bq. "case-insensitive but case-preserving,"
Thinking about it, the "six columns" option more closely matches the RDBMS
experience. Where the case of the string is preserved but then ignored in
queries. It probably also take less to implement.
bq. And providing a comparator per locale is clearly insane.
I would imagine the collation being a comparator property that was used to
construct the java.text.Collator - e.g
UTF8Type("query_collation"="english_CI_AS") for english local, case
insensitive, accent sensitive. Would need to do some research on how to use the
java.text.Collator correctly though.
Still think there may be a need, but it's more than a drop in comparator.
> 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
