[
https://issues.apache.org/jira/browse/CASSANDRA-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276807#comment-13276807
]
Jonathan Ellis commented on CASSANDRA-4245:
-------------------------------------------
bq. I think 3 columns is what we want
In that case, I think our message should be, "call toLowerCase client side."
It's virtually painless and doesn't expose us to the mess that is
"case-insensitive but case-preserving," which is what I think you're suggesting.
bq. There is a default case insensitive comparator in java
"Note that this Comparator does not take locale into account, and will result
in an unsatisfactory ordering for certain locales. The java.text package
provides Collators to allow locale-sensitive ordering."
I'm starting to think that Brandon is right, and trying to do this in a
unicode-aware world is a world of hurt. In particular, a single
"case-insensitive" comparator will never provide the "right" ordering for all
locales. And providing a comparator per locale is clearly insane.
> 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
