Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8334910358 for ; Wed, 21 Aug 2013 20:54:53 +0000 (UTC) Received: (qmail 94104 invoked by uid 500); 21 Aug 2013 20:54:53 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 94071 invoked by uid 500); 21 Aug 2013 20:54:53 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 94062 invoked by uid 99); 21 Aug 2013 20:54:53 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Aug 2013 20:54:53 +0000 Date: Wed, 21 Aug 2013 20:54:53 +0000 (UTC) From: "Lars Hofhansl (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-9272) A simple parallel, unordered scanner 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/HBASE-9272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13746834#comment-13746834 ] Lars Hofhansl commented on HBASE-9272: -------------------------------------- Oh yeah. You'd have to instantiate the ParallelScanner object yourself in the client anyway. > A simple parallel, unordered scanner > ------------------------------------ > > Key: HBASE-9272 > URL: https://issues.apache.org/jira/browse/HBASE-9272 > Project: HBase > Issue Type: New Feature > Reporter: Lars Hofhansl > Assignee: Lars Hofhansl > Priority: Minor > Attachments: ParallelClientScanner.java > > > The contract of ClientScanner is to return rows in sort order. That limits the order in which region can be scanned. > I propose a simple ParallelScanner that does not have this requirement and queries regions in parallel, return whatever gets returned first. > This is generally useful for scans that filter a lot of data on the server, or in cases where the client can very quickly react to the returned data. > I have a simple prototype (doesn't do error handling right, and might be a bit heavy on the synchronization side - it used a BlockingQueue to hand data between the client using the scanner and the threads doing the scanning, it also could potentially starve some scanners long enugh to time out at the server). > On the plus side, it's only a 130 lines of code. :) -- 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: http://www.atlassian.com/software/jira