hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2503) REST Insert / Select
Date Sun, 30 Dec 2007 20:59:43 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12555027
] 

Hadoop QA commented on HADOOP-2503:
-----------------------------------

+1 overall.  Here are the results of testing the latest attachment 
http://issues.apache.org/jira/secure/attachment/12372333/2503.patch
against trunk revision r607330.

    @author +1.  The patch does not contain any @author tags.

    javadoc +1.  The javadoc tool did not generate any warning messages.

    javac +1.  The applied patch does not generate any new compiler warnings.

    findbugs +1.  The patch does not introduce any new Findbugs warnings.

    core tests +1.  The patch passed core unit tests.

    contrib tests +1.  The patch passed contrib unit tests.

Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1437/testReport/
Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1437/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1437/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1437/console

This message is automatically generated.

> 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
>            Assignee: Bryan Duxbury
>            Priority: Critical
>             Fix For: 0.16.0
>
>         Attachments: 2503.patch
>
>
> 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.


Mime
View raw message