[ https://issues.apache.org/jira/browse/ACCUMULO-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789818#comment-13789818 ]
ASF subversion and git services commented on ACCUMULO-1566: ----------------------------------------------------------- Commit ff95c7147d210171fef3824eae399b7384cdaff9 in branch refs/heads/ACCUMULO-1566 from [~elserj] [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=ff95c71 ] ACCUMULO-1566 Pass down the readaheadThreshold parameter from the client to the server so that the same limit is adhered to by the server in regards to pipelining. > Add ability for client to start Scanner readahead immediately > ------------------------------------------------------------- > > Key: ACCUMULO-1566 > URL: https://issues.apache.org/jira/browse/ACCUMULO-1566 > Project: Accumulo > Issue Type: Improvement > Components: client > Reporter: Josh Elser > Assignee: Josh Elser > Fix For: 1.6.0 > > > When the client cares about getting results in sorted order, the > BatchScanner, as nice as it is, is mostly irrelevant. > One interesting property of the Scanner is that it will begin to pre-fetch > more results after the 3rd batch of results has been fetched from the server. > Clients may have an idea of the number of records that will be returned by a > scan, and thus will have an idea about how they want to control such a > readahead. It would be nice to allow the client to control after how many > batches the readahead thread starts. -- This message was sent by Atlassian JIRA (v6.1#6144)