accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris McCubbin (JIRA)" <>
Subject [jira] [Reopened] (ACCUMULO-261) Scanner should support batch size specified in bytes
Date Mon, 18 Mar 2013 19:38:15 GMT


Chris McCubbin reopened ACCUMULO-261:

I'm running into this as well. I guess my main issue is that at scan time, the table.scan.max.memory
setting has higher priority than the batch size and any batch size that would return more
entries than that is just ignored. I'd also like to do this for only certain scans due to
memory constraints. 1M is enough for most uses but in this special case I'd like to have more.
> Scanner should support batch size specified in bytes
> ----------------------------------------------------
>                 Key: ACCUMULO-261
>                 URL:
>             Project: Accumulo
>          Issue Type: New Feature
>          Components: client
>            Reporter: John Vines
>            Assignee: Billie Rinaldi
> Currently the scanner allows a user to set batch size in numbers of entries. Unfortunately
this isn't too useful if you have widely varied entry size and you want to keep your internal
footprint within a threshold. So we should also allow users to set batch size in maximum number
of bytes to bring back.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message