You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Jean-Marc Spaggiari (JIRA)" <ji...@apache.org> on 2015/05/20 15:01:00 UTC
[jira] [Created] (HBASE-13721) Improve shell scan performances when
using LIMIT
Jean-Marc Spaggiari created HBASE-13721:
-------------------------------------------
Summary: 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
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)