Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 9 Jul 2017 02:55:00 +0000 (UTC)
From: "Duo Zhang (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13085740.1499568413000.201363.1499568900030@Atlassian.JIRA>
In-Reply-To: <JIRA.13085740.1499568413000@Atlassian.JIRA>
References: <JIRA.13085740.1499568413000@Atlassian.JIRA> <JIRA.13085740.1499568413600@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HBASE-18348) The implementation of
 AsyncTableRegionLocator does not follow the javadoc
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 09 Jul 2017 02:55:06 -0000


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

Duo Zhang commented on HBASE-18348:
-----------------------------------

For me, I do not like the 'reload' option. It gives user an impression that this method will modify the cache if reload is true. This makes the implementation a little more complicated as there are more possible races.

So I suggest that we change the parameter name from 'reload' to 'bypassCache', or some others words(sorry, poor English) which have the same meaning that we will fetch the HRegionLocation directly from HBase cluster.

Thanks.

> The implementation of AsyncTableRegionLocator does not follow the javadoc
> -------------------------------------------------------------------------
>
>                 Key: HBASE-18348
>                 URL: https://issues.apache.org/jira/browse/HBASE-18348
>             Project: HBase
>          Issue Type: Bug
>          Components: asyncclient, Client
>    Affects Versions: 2.0.0-alpha-1
>            Reporter: Duo Zhang
>            Priority: Critical
>             Fix For: 2.0.0-alpha-2
>
>
> The reload parameter is just ignored.
> Need to fix this before 2.0.0 release.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)