Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 20 May 2015 14:39:00 +0000 (UTC)
From: "Jean-Marc Spaggiari (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12831364.1432126856000.169378.1432132740609@Atlassian.JIRA>
In-Reply-To: <JIRA.12831364.1432126856000@Atlassian.JIRA>
References: <JIRA.12831364.1432126856000@Atlassian.JIRA>
 <JIRA.12831364.1432126856373@arcas>
Subject: [jira] [Updated] (HBASE-13721) Improve shell scan performances when
 using LIMIT
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-13721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Marc Spaggiari updated HBASE-13721:
----------------------------------------
    Status: Patch Available  (was: Open)

> Improve shell scan performances when using LIMIT
> ------------------------------------------------
>
>                 Key: HBASE-13721
>                 URL: https://issues.apache.org/jira/browse/HBASE-13721
>             Project: HBase
>          Issue Type: Bug
>          Components: shell
>    Affects Versions: 1.1.0
>            Reporter: Jean-Marc Spaggiari
>            Assignee: Jean-Marc Spaggiari
>         Attachments: HBASE-13721-v0-trunk.txt
>
>
> When doing a scan which is expected to return the exact same number of rows as the LIMIT we give, we still scan the entire table until we return the row(s) and then test the numbers of rows we have. This can take a lot of time.
> Example:
> scan 'sensors', { COLUMNS => ['v:f92acb5b-079a-42bc-913a-657f270a3dc1'], STARTROW => '000a', LIMIT => 1 }
> This is because we will break on the limit condition AFTER we ask for the next row. If there is none, we scan the entire table than exit.
> Goal of this patch is to handle this specific case without impacting the others.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)