Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 17 Jan 2013 17:48:25 +0000 (UTC)
From: "Lars Hofhansl (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12626006.1357300051022.153264.1358444905046@arcas>
In-Reply-To: <JIRA.12626006.1357300051022@arcas>
References: <JIRA.12626006.1357300051022@arcas>
Subject: [jira] [Commented] (HBASE-7495) parallel scanner seek in
 StoreScanner's constructor
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/HBASE-7495?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1355=
6406#comment-13556406 ]=20

Lars Hofhansl commented on HBASE-7495:
--------------------------------------

I can see that for Gets it would be an improvement.
               =20
> parallel scanner seek in StoreScanner's constructor
> ---------------------------------------------------
>
>                 Key: HBASE-7495
>                 URL: https://issues.apache.org/jira/browse/HBASE-7495
>             Project: HBase
>          Issue Type: Bug
>          Components: Scanners
>    Affects Versions: 0.94.3, 0.96.0
>            Reporter: liang xie
>            Assignee: liang xie
>         Attachments: HBASE-7495.txt
>
>
> seems there's a potential improvable space before doing scanner.next:
> {code:title=3DStoreScanner.java|borderStyle=3Dsolid}
>     if (explicitColumnQuery && lazySeekEnabledGlobally) {
>       for (KeyValueScanner scanner : scanners) {
>         scanner.requestSeek(matcher.getStartKey(), false, true);
>       }
>     } else {
>       for (KeyValueScanner scanner : scanners) {
>         scanner.seek(matcher.getStartKey());
>       }
>     }
> {code}=20
> we can do scanner.requestSeek or scanner.seek in parallel, instead of cur=
rent serialization, to reduce latency for special case.
> Any ideas on it ?  I'll have a try if the comments/suggestions are positi=
ve=EF=BC=9A=EF=BC=89

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira