[
https://issues.apache.org/jira/browse/ACCUMULO-840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487940#comment-13487940
]
David Medinets commented on ACCUMULO-840:
-----------------------------------------
>From the dev mailing list:
John: Why not just have a configuration in the xml file for setting a global >
charset? This way we avoid hard coded settings but also avoid the issue of
shared vm issues.
Drew: +1 for a configuration file property -- perhaps this could be worked into
the Encoding class
> Allow String-based getBytes calls to pick Charset ending from JVM setting.
> --------------------------------------------------------------------------
>
> Key: ACCUMULO-840
> URL: https://issues.apache.org/jira/browse/ACCUMULO-840
> Project: Accumulo
> Issue Type: Improvement
> Affects Versions: 1.5.0
> Reporter: David Medinets
> Assignee: David Medinets
> Priority: Minor
> Fix For: 1.5.0
>
>
> ACCUMULO-836 changed all String-based getBytes() calls to use the UTF-8
> standard. However, there is a JVM setting called "jvm.encoding" that should
> be honored. See
> http://stackoverflow.com/questions/361975/setting-the-default-java-character-encoding
> for a discussion of JAVA_TOOL_OPTIONS which might be relevant to this topic.
> http://javarevisited.blogspot.com/2012/01/get-set-default-character-encoding.html
> is also a good page to read especially the comment on how character encoding
> is cached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
