The current scanner implementation for scanner stores state and hence not very suitable for REST server failure scenarios. The current JIRA proposes to implement a stateless scanner. In the first version of the patch, a new resource class "ScanResource" has been added and all the scan parameters will be specified as query params.
The following are the scan parameters
startrow - The start row for the scan.
endrow - The end row for the scan.
columns - The columns to scan.
starttime, endtime - To only retrieve columns within a specific range of version timestamps,both start and end time must be specified.
maxversions - To limit the number of versions of each column to be returned.
batchsize - To limit the maximum number of values returned for each call to next().
limit - The number of rows to return in the scan operation.
More on start row, end row and limit parameters.
1. If start row, end row and limit not specified, then the whole table will be scanned.
2. If start row and limit (say N) is specified, then the scan operation will return N rows from the start row specified.
3. If only limit parameter is specified, then the scan operation will return N rows from the start of the table.
4. If limit and end row are specified, then the scan operation will return N rows from start of table till the end row. If the end row is
reached before N rows ( say M and M < N ), then M rows will be returned to the user.
5. If start row, end row and limit (say N ) are specified and N < number of rows between start row and end row, then N rows from start row
will be returned to the user. If N > (number of rows between start row and end row (say M), then M number of rows will be returned to the