[
https://issues.apache.org/jira/browse/CASSANDRA-9626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14598534#comment-14598534
]
Joshua McKenzie commented on CASSANDRA-9626:
--------------------------------------------
bq. I am a little nervous around changing what we do by default in case
someway somehow someone is relying on it.
bq. 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
So what happens when a) someone has been relying on the old behavior, and b)
they upgrade? We put them between a rock and a hard place, they most will
likely change the setting not realizing they were even relying on the old
behavior, and then they have an upgraded cluster and aren't getting back the
data they expected. No amount of NEWS.txt changes will prevent this
unfortunately.
For file encoding, UTF-8 will probably work. When you were beefing up some
testing [~aweisberg] and broke the build on Windows, I set
{{JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF8}} locally and on our build servers and
have been running with it since without issue, so I'd be comfortable going that
route assuming the file encoding doesn't restrict the character set people can
store in their DB.
> 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)
