[
https://issues.apache.org/jira/browse/HBASE-13721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14553545#comment-14553545
]
Hudson commented on HBASE-13721:
--------------------------------
FAILURE: Integrated in HBase-0.98 #996 (See
[https://builds.apache.org/job/HBase-0.98/996/])
HBASE-13721 - Improve shell scan performances when using LIMIT(JMS) (apurtell:
rev 2b035259dc16503b1ff67f6ea577ca588cc33b68)
* hbase-shell/src/main/ruby/hbase/table.rb
> 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
> Fix For: 2.0.0, 0.98.13, 1.0.2, 1.2.0, 1.1.1
>
> 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)
