[
https://issues.apache.org/jira/browse/HBASE-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678437#action_12678437
]
Jonathan Chambers commented on HBASE-1227:
------------------------------------------
Hi stack,
I think I'm right in saying that the various APIs now use:
Java => stopRow
Thrift => stopRow (at least in the ruby version)
REST => stop_row
However the wiki and docs pages say:
Java => stopRow (http://hadoop.apache.org/hbase/docs/current/api/index.html)
Thrift => *endRow* (http://wiki.apache.org/hadoop/Hbase/ThriftApi )
REST => *end_row* (http://wiki.apache.org/hadoop/Hbase/HbaseRest)
So I guess the docs are just out of date right?
Jon
> 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.
