[jira] [Updated] (HBASE-7621) REST server doesn't support binary row keys
[ https://issues.apache.org/jira/browse/HBASE-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith David Winkler updated HBASE-7621: --- Fix Version/s: 2.0.0 Release Note: REST server now supports binary row keys with any character or byte. Affects Version/s: 2.0.0 Status: Patch Available (was: Open) > 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.98.4, 0.95.2, 0.94.0, 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)
[jira] [Updated] (HBASE-7621) REST server doesn't support binary row keys
[ https://issues.apache.org/jira/browse/HBASE-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith David Winkler updated HBASE-7621: --- Attachment: HBASE-7621.master.001.patch Attached patch described in comments. > 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 >Assignee: Keith David Winkler > 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)
[jira] [Updated] (HBASE-7621) REST server doesn't support binary row keys
[ https://issues.apache.org/jira/browse/HBASE-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith David Winkler updated HBASE-7621: --- Attachment: (was: HBASE-7621.master.002.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 >Assignee: Keith David Winkler > > 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)
[jira] [Updated] (HBASE-7621) REST server doesn't support binary row keys
[ https://issues.apache.org/jira/browse/HBASE-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith David Winkler updated HBASE-7621: --- Attachment: HBASE-7621.master.002.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 >Assignee: Keith David Winkler > Attachments: HBASE-7621.master.002.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)
[jira] [Updated] (HBASE-7621) REST server doesn't support binary row keys
[ https://issues.apache.org/jira/browse/HBASE-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-7621: -- Assignee: Keith David Winkler > 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 >Assignee: Keith David Winkler > > 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)
[jira] [Updated] (HBASE-7621) REST server doesn't support binary row keys
[ https://issues.apache.org/jira/browse/HBASE-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Kellogg updated HBASE-7621: Affects Version/s: 0.98.4 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)
[jira] [Updated] (HBASE-7621) REST server doesn't support binary row keys
[ https://issues.apache.org/jira/browse/HBASE-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-7621: -- Assignee: (was: Andrew Purtell) 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 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.2#6252)
[jira] [Updated] (HBASE-7621) REST server doesn't support binary row keys
[ https://issues.apache.org/jira/browse/HBASE-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-7621: -- Affects Version/s: 0.96.0 Assignee: Andrew Purtell 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.96.0 Reporter: Craig Muchinsky Assignee: Andrew Purtell 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 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
