Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 14 Mar 2013 02:36:13 +0000 (UTC)
From: "Enis Soztutar (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12636672.1363127738335.438664.1363228573612@arcas>
In-Reply-To: <JIRA.12636672.1363127738335@arcas>
References: <JIRA.12636672.1363127738335@arcas>
Subject: [jira] [Updated] (HBASE-8085) Backport the fix for
 Bytes.toStringBinary() into 94 (HBASE-6991)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Enis Soztutar updated HBASE-8085:
---------------------------------

      Resolution: Fixed
    Release Note: This patch changes Bytes.toStringBinary() and Bytes.toBytesBinary() to escape the character "\". Unprintable characters are escaped using "\\x%02X" format, but "\" was not escaped properly leading to irreversible ser/de using toStringBinary() -> toBytesBinary(). 
    Hadoop Flags: Incompatible change,Reviewed
          Status: Resolved  (was: Patch Available)

Committed this. Thanks Tianying. 
                
> Backport the fix for Bytes.toStringBinary() into 94 (HBASE-6991)
> ----------------------------------------------------------------
>
>                 Key: HBASE-8085
>                 URL: https://issues.apache.org/jira/browse/HBASE-8085
>             Project: HBase
>          Issue Type: Bug
>          Components: util
>    Affects Versions: 0.94.5
>            Reporter: Tianying Chang
>            Assignee: Tianying Chang
>             Fix For: 0.94.7
>
>         Attachments: HBASE-8085.patch, HBASE-8085-v2.patch
>
>
> there is a bug in Bytes.toStringBinary(), which will return the same string for 1) byte[] a = {'\\', 'x', 'D', 'A'} 2) "\xDA". 
> It seems this bug has already been fixed in trunk with HBASE 6991. We should backport it to 94. 

--
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