[
https://issues.apache.org/jira/browse/HBASE-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426714#comment-15426714
]
Keith David Winkler commented on HBASE-7621:
--------------------------------------------
Updated jira title to reflect that the problem was in the REST client
(RemoteHTable) and not the server.
> 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
>
> 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)
