hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Chambers (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1227) REST server ignores start_row and end_row arguments in scanner request
Date Mon, 02 Mar 2009 13:41:56 GMT

    [ https://issues.apache.org/jira/browse/HBASE-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677984#action_12677984

Jonathan Chambers commented on HBASE-1227:

Hi Sishen,

I agree, it should use end_row if that's what the other interfaces use.

BTW, I was playing with your ruby client (http://github.com/sishen/hbase-ruby/tree/master)
and noticed that some methods are broken under the environment described above. I suspect
the content of messages returned by HBase has changed slightly. I've fixed your code and will
push it back to github as a fork but, should you decide to merge it, you may want to check
the diff for inelegant code (I'm new to ruby).

Also, I thought it might be useful to have a HBase wiki page discussing the pros and cons
of the REST and Thrift interfaces, perhaps with use cases and basic benchmarks. What do you
think? Have you got any thoughts/data on this?



> REST server ignores start_row and end_row arguments in scanner request
> ----------------------------------------------------------------------
>                 Key: HBASE-1227
>                 URL: https://issues.apache.org/jira/browse/HBASE-1227
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: rest
>    Affects Versions: 0.20.0
>         Environment: HBASE: Version: 0.20.0-dev, r743660, Mon Feb 23 13:11:13 GMT 2009
> OS: Linux hardy-vm 2.6.24-23-generic #1 SMP Mon Jan 26 00:13:11 UTC 2009 i686 GNU/Linux
> JAVA: Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
>            Reporter: Jonathan Chambers
>            Assignee: sishen
> When issuing a command like:
>   POST /api/users/scanner?column=habbit:football&start_row=Alice&end_row=Bob
> The resultant scanner appears to ignore the start_row and end_row constraints, so that
a command like:
>   POST /api/users/scanner/1?limit=1000
> returns results outside of the specified range e.g. the row for "William" will be returned.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message