[
https://issues.apache.org/jira/browse/CASSANDRA-9626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14598291#comment-14598291
]
Ariel Weisberg commented on CASSANDRA-9626:
-------------------------------------------
Postgres has the same behavior of inheriting the default locale so I am a
little nervous around changing what we do by default in case someway somehow
someone is relying on it.
What we can do is set defaults in the configuration and then at startup fail
fast if it doesn't match the system locale with an error informing the operator
what config they need to change. But we shouldn't require that the locale set
for C* match the locale for the entire system so they also have to be able to
differ.
There are three settings in question. For file encoding it seem like
[~JoshuaMcKenzie] might care. What is that going to do on Windows? I think we
should be consistent and just hardcode UTF. We shouldn't be relying on the
default encoding anyways (should always pass it in).
For language and locale I think we want do the fail fast if it doesn't match
thing and then let them decide if they want it to differ.
> Make C* work in all locales
> ---------------------------
>
> Key: CASSANDRA-9626
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9626
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Robert Stupp
> Assignee: Robert Stupp
> Priority: Minor
> Attachments: 9626.txt
>
>
> Default locale and default charset has immediate effect on how strings are
> encoded and handles - e.g. via {{String.toLowerCase()}} or {{new
> String(byte[])}}.
> Problems with different default locales + charsets don't become obvious for
> US and most European regional settings. But some regional OS settings will
> cause severe errors. Example: {{"BILLY".toLowerCase()}} returns {{bılly}}
> with Locale tr_TR (take a look at the second letter - it's an i without the
> dot).
> (ref:
> http://blog.thetaphi.de/2012/07/default-locales-default-charsets-and.html)
> It's not a problem I'm currently facing, but it could become a problem for
> some users. A quick fix could be to set default locale and charset in the
> start scripts - maybe that's all we need.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
