You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Mustafa Kuscu (JIRA)" <ji...@apache.org> on 2018/02/13 11:02:00 UTC
[jira] [Commented] (CASSANDRA-12588) Cannot find column durable_wrıtes
[ https://issues.apache.org/jira/browse/CASSANDRA-12588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362138#comment-16362138 ]
Mustafa Kuscu commented on CASSANDRA-12588:
-------------------------------------------
Some example runs from command line:
OK:
{{ LANG= cassandra -f }}
OK:
{{ LANG=en_US.UTF-8 cassandra -f}}
But this FAILS:
{{ LANG=tr_TR.UTF-8 cassandra -f }}
I believe there are many Cassandra installations in Turkey who can serve Turkish content properly. Therefore although locale is instructed to JVM from the environment, the purpose of localization has no use from within Cassandra context. Is this correct?
Also, it is easy to get around this by ignoring LANG environment variable as can be seen in examples above.
As a permanent solution, I would like to propose, to force Locale.English to be used during startup. Something like the following
{{java.util.Locale.setDefault(java.util.Locale.English) }}
to be executed during startup.
Is this possible?
> Cannot find column durable_wrıtes
> ---------------------------------
>
> Key: CASSANDRA-12588
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12588
> Project: Cassandra
> Issue Type: Bug
> Reporter: LLc.
> Priority: Major
>
> help please
> run :
> cassandra -f
> ERROR 17:00:16 Exception encountered during startup
> java.lang.AssertionError: Cannot find column durable_wrıtes
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org