Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 24 Mar 2011 18:06:05 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <1373239518.8945.1300989965734.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1194039026.8773.1300986786587.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-2379) ByteBufferUtil#bytes(String)
 can produce undesired results for some characters
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010806#comment-13010806 ] 

Jonathan Ellis commented on CASSANDRA-2379:
-------------------------------------------

where are we still using default charset after CASSANDRA-2367?

> 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