[
https://issues.apache.org/jira/browse/HBASE-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856480#action_12856480
]
Paul Kist commented on HBASE-2438:
----------------------------------
Jonathan,
That is correct. Column pagination and row pagination need to be handled
separately. I had initially looked at augmenting the PageFilter, however the
issue with row pagination at the Filter level is the fact that the Filters run
within the context of a single region server, unaware of any other rows that
may be returned from other Filters on another region. That being the case,
Row pagination is a different ballgame altogether, so I decided to keep the
functionality of this Filter specific to columns.
> Addition of a Column Pagination Filter
> --------------------------------------
>
> Key: HBASE-2438
> URL: https://issues.apache.org/jira/browse/HBASE-2438
> Project: Hadoop HBase
> Issue Type: New Feature
> Components: filters
> Affects Versions: 0.20.3
> Reporter: Paul Kist
> Original Estimate: 8h
> Remaining Estimate: 8h
>
> Client applications may need to do pagination, depending on the number of
> columns returned, it may be more efficient to perform pagination algorithms
> at the database level (similar to SQL's LIMIT and OFFSET). This will be an
> additional filter taking two parameters:
> - page
> - pageSize
> For every row, that gets returned, only a subset of columns are returned
> based on page and pageSize
> If the page / pageSize column goes over the limits, then no results are
> returned from the filter.
> A practical example for using a filter like this may be for folks doing
> Row-based indexing with Hbase.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
