You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2011/03/17 21:40:29 UTC
[jira] Commented: (HBASE-3662) REST server does not respect client
supplied max versions when creating scanner
[ https://issues.apache.org/jira/browse/HBASE-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008119#comment-13008119 ]
Andrew Purtell commented on HBASE-3662:
---------------------------------------
That seems it, good catch Gary. I'll commit a trivial patch to 0.90 and trunk after tests pass locally.
> REST server does not respect client supplied max versions when creating scanner
> -------------------------------------------------------------------------------
>
> Key: HBASE-3662
> URL: https://issues.apache.org/jira/browse/HBASE-3662
> Project: HBase
> Issue Type: Bug
> Components: rest
> Affects Versions: 0.90.1
> Reporter: Gary Helmling
> Assignee: Andrew Purtell
>
> In {{org.apache.hadoop.hbase.rest.ScannerResource.update()}}, where a new scanner is created on the server, we don't seem to respect the max versions value sent by the client:
> {noformat}
> RowSpec spec = new RowSpec(model.getStartRow(), endRow,
> model.getColumns(), model.getStartTime(), model.getEndTime(), 1);
> {noformat}
> Looks to me like the last argument of "1" should instead be {{model.getMaxVersions()}}.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira