You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Jonathan Chambers (JIRA)" <ji...@apache.org> on 2009/02/28 11:52:12 UTC
[jira] Created: (HBASE-1227) REST server ignores start_row and
end_row arguments in scanner request
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
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 http://localhost:60050/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.
[jira] Commented: (HBASE-1227) REST server ignores start_row and
end_row arguments in scanner request
Posted by "Jonathan Chambers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678151#action_12678151 ]
Jonathan Chambers commented on HBASE-1227:
------------------------------------------
or... maybe the 0.19 and 0.20 versions of hbase-ruby should be in different branches? Or, at least tagged as being for different versions. That way, anyone who is tied to using HBase 0.19 can still get hold of a working ruby client. Just an idea...
> 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.
[jira] Commented: (HBASE-1227) REST server ignores start_row and
end_row arguments in scanner request
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678425#action_12678425 ]
stack commented on HBASE-1227:
------------------------------
In the java api its stopRow so it would seem to make sense using stop_row, no? When you talk about "other modules", to what are you referring?
> 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.
[jira] Assigned: (HBASE-1227) REST server ignores start_row and
end_row arguments in scanner request
Posted by "sishen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
sishen reassigned HBASE-1227:
-----------------------------
Assignee: sishen
> 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.
[jira] Commented: (HBASE-1227) REST server ignores start_row and
end_row arguments in scanner request
Posted by "sishen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677989#action_12677989 ]
sishen commented on HBASE-1227:
-------------------------------
Hi, Jonathan.
My ruby client is compatible with the release version which is 0.19.0 but not v0.2.
You see that a big refactor of REST module has already be implemented in 0.2 and some apis are changed.
I have the plan to update my ruby lib to keep compatible with 0.2 but think not urgent.
Anyway, thanks for your patch. Can you kindly send me the diffs? :)
> 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.
[jira] Resolved: (HBASE-1227) REST server ignores start_row and
end_row arguments in scanner request
Posted by "sishen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
sishen resolved HBASE-1227.
---------------------------
Resolution: Won't Fix
Fix Version/s: 0.20.0
> 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
> Fix For: 0.20.0
>
>
> 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.
[jira] Updated: (HBASE-1227) REST server ignores start_row and
end_row arguments in scanner request
Posted by "Jonathan Chambers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Chambers updated HBASE-1227:
-------------------------------------
Description:
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.
was:
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 http://localhost:60050/api/users/scanner/1?limit=1000
returns results outside of the specified range e.g. the row for "William" will be returned.
> 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
>
> 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.
[jira] Issue Comment Edited: (HBASE-1227) REST server ignores
start_row and end_row arguments in scanner request
Posted by "sishen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677886#action_12677886 ]
yedingding@gmail.com 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: yedingding@gmail.com):
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.
[jira] Commented: (HBASE-1227) REST server ignores start_row and
end_row arguments in scanner request
Posted by "Jonathan Chambers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678149#action_12678149 ]
Jonathan Chambers commented on HBASE-1227:
------------------------------------------
Yeah, I guessed your original code was for an earlier version.
I've forked the project here: http://github.com/jmchambers/hbase-ruby/tree/master
The diff can be viewed here: http://github.com/jmchambers/hbase-ruby/commit/19f567536e806e6cd7b20944344b19ba2245e3e7
I've sent you a "pull request" through github, so you should be able to merge in my changes assuming they're ok.
Cheers,
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.
[jira] Commented: (HBASE-1227) REST server ignores start_row and
end_row arguments in scanner request
Posted by "Jonathan Chambers (JIRA)" <ji...@apache.org>.
[ 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?
Cheers,
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.
[jira] Commented: (HBASE-1227) REST server ignores start_row and
end_row arguments in scanner request
Posted by "sishen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678543#action_12678543 ]
sishen commented on HBASE-1227:
-------------------------------
stack: sorry, it's my mistake while refering to earlier version.
Jon: i'll create a branch for v0.19 and update the lib in days. Thanks.
> 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
> Fix For: 0.20.0
>
>
> 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.
[jira] Issue Comment Edited: (HBASE-1227) REST server ignores
start_row and end_row arguments in scanner request
Posted by "Jonathan Chambers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678437#action_12678437 ]
jmchambers edited comment on HBASE-1227 at 3/3/09 1:00 PM:
------------------------------------------------------------------
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 wikis are out of date right?
Jon
was (Author: jmchambers):
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.
[jira] Commented: (HBASE-1227) REST server ignores start_row and
end_row arguments in scanner request
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678615#action_12678615 ]
stack commented on HBASE-1227:
------------------------------
Thanks Jonathan for finding the doc. issues. I just made the changes up on the wiki.
> 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
> Fix For: 0.20.0
>
>
> 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.
[jira] Commented: (HBASE-1227) REST server ignores start_row and
end_row arguments in scanner request
Posted by "sishen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677886#action_12677886 ]
sishen commented on HBASE-1227:
-------------------------------
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.
[jira] Commented: (HBASE-1227) REST server ignores start_row and
end_row arguments in scanner request
Posted by "Jonathan Chambers (JIRA)" <ji...@apache.org>.
[ 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.