[
https://issues.apache.org/jira/browse/HBASE-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797783#action_12797783
]
Andrew Purtell commented on HBASE-2093:
---------------------------------------
bq. About to release 0.20.3 so punting to 0.20.4
No problem J-D. I'm looking at this one today though, if that matters.
bq. I guess one workaround would be to encode the row keys if they are known to
be built like this.
Based on the example given by the reporter, the client is already hex encoding
URL metacharacters. If a client submits a row with the key
{{http%3A%2F%2Fwww.google.com%2F}}
it should be passed through as-is to HBase, not URL-decoded somehow. I hope to
fix this without resorting to requiring users to base64 encode their row and
column specifiers.
> [stargate] RowSpec parse bug
> ----------------------------
>
> Key: HBASE-2093
> URL: https://issues.apache.org/jira/browse/HBASE-2093
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 0.20.4, 0.21.0
>
>
> From mike anderson up on hbase-user@:
> {quote}
> Trying to create a row in hbase from ruby with row key
> "http://www.google.com"; produces this exception
> {noformat}
> 2010-01-05 11:40:53.972::WARN: /cached_web_pages/http%3A%2F%
> 2Fwww.google.com%2F/
> java.lang.IllegalArgumentException: java.lang.NumberFormatException: For
> input string: "www.google.com"
> at org.apache.hadoop.hbase.stargate.RowSpec.parseTimestamp(RowSpec.java:171)
> at org.apache.hadoop.hbase.stargate.RowSpec.(RowSpec.java:55)
> at org.apache.hadoop.hbase.stargate.RowResource.(RowResource.java:62)
> at
> org.apache.hadoop.hbase.stargate.TableResource.getRowResource(TableResource.java:117)
> [...]
> {noformat}
> {quote}
> Move to 0.20.4 if this gets in the way of the 0.20.3 release before I can
> look at it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
