[
https://issues.apache.org/jira/browse/CASSANDRA-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010776#comment-13010776
]
Nate McCall commented on CASSANDRA-2379:
----------------------------------------
We have a testcase for this in Hector which periodically fails on macs (uses
ByteBufferUtil method for verification of results):
https://github.com/rantav/hector/blob/master/core/src/test/java/me/prettyprint/cassandra/serializers/StringSerializerTest.java
> ByteBufferUtil#bytes(String) can produce undesired results for some characters
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-2379
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2379
> Project: Cassandra
> Issue Type: Bug
> Reporter: Nate McCall
> Attachments: 2379.txt
>
>
> The difference between getBytes(java.nio.charset.Charset) vs.
> getBytes("[charsetname]") on some platforms (mac it seems) can be
> substantial. From the java.lang.String javadoc for the former:
> This method always replaces malformed-input and unmappable-character
> sequences with this charset's default replacement byte array...
> vs. the latter:
> The behavior of this method when this string cannot be encoded in the default
> charset is unspecified.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
