Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0B65910A06 for ; Tue, 8 Oct 2013 19:33:01 +0000 (UTC) Received: (qmail 57258 invoked by uid 500); 8 Oct 2013 19:32:55 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 56974 invoked by uid 500); 8 Oct 2013 19:32:46 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 56944 invoked by uid 99); 8 Oct 2013 19:32:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Oct 2013 19:32:45 +0000 Date: Tue, 8 Oct 2013 19:32:45 +0000 (UTC) From: "Josh Elser (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-1566) Add ability for client to start Scanner readahead immediately MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789581#comment-13789581 ] Josh Elser commented on ACCUMULO-1566: -------------------------------------- [~kturner], any problem with me opening up a new ticket for that? I think I see where the work needs to happen in TabletServer, but I'll definitely need some review before pushing the server-side changes. > 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)