Unfortunately I have to punt this to 0.20.4 but, looking into the
issue, is seems that the row key is parsed in a different way because
it's expecting something like this:
path := '/' <table> '/' <row> '/' <column> ( ':' <qualifier> )?
( '/' <timestamp> )?
I guess that a workaround would be to simply encode the row keys on
the client-side. (eg base64)
J-D
On Tue, Jan 5, 2010 at 1:59 PM, Andrew Purtell <[email protected]> wrote:
> Hi Mike,
>
> I am the Stargate maintainer. You can address this type of issue to me, or
> file
> jiras kindly with a subject that begins "[stargate]". In this case I have done
> that already and will take a look at this shortly. Please see
>
> https://issues.apache.org/jira/browse/HBASE-2093
>
> I have to catch a flight back from Taipei today so it may be 48 hours or so
> before I can look at it.
>
>
> Best regards,
>
> - Andy
>
>
>
> ----- Original Message ----
>> From: mike anderson <[email protected]>
>> To: [email protected]
>> Sent: Wed, January 6, 2010 12:54:29 AM
>> Subject: Stargate API
>>
>> I'm using this new hbase-ruby gem that
>> utilizes the Stargate API, so I'm not exactly sure who to address this bug
>> to.
>>
>> Trying to create a row in hbase from ruby with row key "
>> http://www.google.com"; produces this exception
>>
>> 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)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> [...]
>
>
>
>
>
