Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 17 Jan 2013 12:34:13 +0000 (UTC)
From: "Matteo Bertozzi (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12627945.1358376458101.151825.1358426053307@arcas>
In-Reply-To: <JIRA.12627945.1358376458101@arcas>
References: <JIRA.12627945.1358376458101@arcas>
Subject: [jira] [Commented] (HBASE-7592)
 HConnectionManager.getHTableDescriptor() compares too much
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-7592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556122#comment-13556122 ] 

Matteo Bertozzi commented on HBASE-7592:
----------------------------------------

I was thinking to a compatibility issue with someone that doesn't have the overload with the list as argument, but looking at the history the overload is there since the first implementation. HBASE-451 https://github.com/apache/hbase/commit/80b68495b5a67bcfc1db038e500c500c9977acc9
                
> HConnectionManager.getHTableDescriptor() compares too much
> ----------------------------------------------------------
>
>                 Key: HBASE-7592
>                 URL: https://issues.apache.org/jira/browse/HBASE-7592
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 0.94.4
>            Reporter: Matteo Bertozzi
>            Assignee: Matteo Bertozzi
>            Priority: Trivial
>             Fix For: 0.94.5
>
>         Attachments: HBASE-7592-v0.patch, HBASE-7592-v1.patch
>
>
> in 0.94 getHTableDescriptor() looks at every htd instead of returning at the first found. (Trunks has already the early exit)
> {code}
> for (HTableDescriptor htd: htds) {
>   if (Bytes.equals(tableName, htd.getName())) {
>     hTableDescriptor = htd;
>   }
> }
> return htableDescriptor
> {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