You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Dylan Hutchison (JIRA)" <ji...@apache.org> on 2015/05/09 17:01:01 UTC

[jira] [Commented] (ACCUMULO-261) Scanner should support batch size specified in bytes

    [ https://issues.apache.org/jira/browse/ACCUMULO-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536625#comment-14536625 ] 

Dylan Hutchison commented on ACCUMULO-261:
------------------------------------------

I'm also running into this issue, though the use case is different.  I have iterators on a BatchScan that perform long-running computation and periodically emit "monitoring" entries to send back to the client that contain info on the progress of the computation.  These monitoring entries emit, say, once every 10 seconds, and when they do, we'd like to send them back to the client right away.  

Only current method to do so is temporarily change the {{table.scan.max.memory}} parameter, which affects other concurrent scans on the same table.  Would be really nice to have a per-scan option on how many entries (or bytes) the tablet server caches before sending to the client.

> Scanner should support batch size specified in bytes
> ----------------------------------------------------
>
>                 Key: ACCUMULO-261
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-261
>             Project: Accumulo
>          Issue Type: New Feature
>          Components: client
>            Reporter: John Vines
>             Fix For: 1.8.0
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)