hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-7621) REST client (RemoteHTable) doesn't support binary row keys
Date Fri, 19 Aug 2016 19:31:21 GMT

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

Andrew Purtell updated HBASE-7621:
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.4.0
     Release Note: RemoteHTable now supports binary row keys with any character or byte by
properly encoding request URLs. This is a both a behavioral change from earlier versions and
an important fix for protocol correctness.  (was: REST server now supports binary row keys
with any character or byte.)
           Status: Resolved  (was: Patch Available)

> REST client (RemoteHTable) doesn't support binary row keys
> ----------------------------------------------------------
>
>                 Key: HBASE-7621
>                 URL: https://issues.apache.org/jira/browse/HBASE-7621
>             Project: HBase
>          Issue Type: Bug
>          Components: REST
>    Affects Versions: 0.94.0, 0.95.2, 0.98.4, 2.0.0
>            Reporter: Craig Muchinsky
>            Assignee: Keith David Winkler
>             Fix For: 2.0.0, 1.4.0
>
>         Attachments: HBASE-7621.master.001.patch
>
>
> The REST server doesn't seem to support using binary (MD5 for example) row keys. I believe
the root cause of this is the use of Bytes.toBytes() in the RowSpec.parseRowKeys() method.
Based on the use of Bytes.toStringBinary() within RemoteHTable.buildRowSpec(), I believe the
converse function Bytes.toBytesBinary() should be used for row key parsing in RowSpec.parseRowKeys().
> I also noticed that the RemoteHTable.buildRowSpec() method isn't URL encoding the row
key, which is a mismatch to the logic in RowSpec.parseRowKeys() which performs URL decoding
for both the start and stop row keys.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message