[
https://issues.apache.org/jira/browse/HBASE-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677886#action_12677886
]
[email protected] edited comment on HBASE-1227 at 3/1/09 8:27 PM:
-------------------------------------------------------
The current implementation use stop_row as the end_row.
So if you use the follow post request, it will work.
POST /api/users/scanner?column=habbit:football&start_row=Alice&*stop_row*=Bob
However, should we use end_row instead to keep consistent with other modules? I
think we should. Any ideas?
was (Author: [email protected]):
The current implementation use stop_row as the end_row.
So if you use the follow post request, it will work.
POST /api/users/scanner?column=habbit:football&start_row=Alice&stop_row=Bob
However, should we use end_row instead to keep consistent with other modules? I
think we should. Any ideas?
> 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.
