[
https://issues.apache.org/jira/browse/HBASE-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856630#action_12856630
]
Paul Kist commented on HBASE-2438:
----------------------------------
Jonathan,
Thanks for the performance tip, I'll definitely include that.
Regarding the readFields and write functions, so you're saying that in
readFields, i'll have to also calculate offset (because that's what's being
called by the serializer which calls the empty constructor)?
Could you point me to an example of how I can test the serialization of a
filter? Thank you
> 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
> Assignee: Paul Kist
> Attachments: hbase-2438-0.20.3.patch
>
> 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
