[
https://issues.apache.org/jira/browse/ACCUMULO-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440009#comment-13440009
]
Josh Elser commented on ACCUMULO-736:
-------------------------------------
Given that all data retrieval from Accumulo is returned to the client via a
Java Iterator, I'm a little confused about the application of such a feature.
If you have many columns in one row, you'll get a Key-Value pair for each
Row-Column at which point it's an exercise for the client not to consume more
than can fit in its memory.
Other applications seem to be solvable through a custom Accumulo Iterator. For
example, if you want to fetch all columns for a row in one call in batches of
size N, this is easily done with an Accumulo Iterator without any core changes.
Please assume I'm an HBase API novice. Can you provide some more concrete
details?
Thanks.
> Add Column Pagination Filter
> ----------------------------
>
> Key: ACCUMULO-736
> URL: https://issues.apache.org/jira/browse/ACCUMULO-736
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Reporter: Pradeep Gollakota
> Assignee: Billie Rinaldi
>
> Client application may need to perform pagination of data depending on the
> number of columns returned. This would be more efficient if the database
> itself handled the pagination.
> Similar to https://issues.apache.org/jira/browse/HBASE-2438
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
