It seems possible that it's not correctly decoding the keys on the
get/deletes. I will look into it when I get back to SF.
On Dec 29, 2007, at 12:51 PM, Billy Pearson (JIRA) wrote:
[ https://issues.apache.org/jira/browse/HADOOP-2503?
page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
tabpanel#action_12554952 ]
Billy Pearson commented on HADOOP-2503:
---------------------------------------
I have not checked if deletes are effect by this should be tested
also.
I thank storing the data urldecoded would be the best solution so
on every query we could just make sure the row key is urldecoded
before running select/inserting/delete code.
REST Insert / Select
--------------------
Key: HADOOP-2503
URL: https://issues.apache.org/jira/browse/
HADOOP-2503
Project: Hadoop
Issue Type: Bug
Components: contrib/hbase
Reporter: Billy Pearson
Priority: Critical
Fix For: 0.16.0
On inserts I submit the row key as urlencoded and its stored that
way with the urlencodeing intact.
But when I select with rest I send the row key as urlencoded as I
stored it and get nothing back. I thank the problem is the rest
interfase is urldecodeing the request before looking up the data
in the table. I can select with the urlencoded row key with the
shell and get results.
This makes data not selectable if it has any urlencodeing chrs.
So 1 of two options I see
Make the insert store the row key after urldecode or make the
select look up the row key the way it is submitted with out
urldecodeing the key.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
