hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith David Winkler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7621) REST server doesn't support binary row keys
Date Wed, 17 Aug 2016 01:40:20 GMT

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

Keith David Winkler commented on HBASE-7621:
--------------------------------------------

Thanks Andrew, that makes sense.  There are probably many folks like me that use RemoteHTable
as a (valuable) tool in their own tests/tools for java codebases. And likely there some projects
out there that use RemoteHTable in production.   The fix for this issue is straightforward,
I'll work on a patch.

> REST server 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
>            Reporter: Craig Muchinsky
>
> 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