hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duo Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17372) Make AsyncTable thread safe
Date Fri, 13 Jan 2017 12:25:26 GMT

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

Duo Zhang commented on HBASE-17372:

Will clean the import .* when commit.

And for {{AsyncTableBuilderBase}}, I think usually a Builder is not thread safe? Like the
old Table implementation, it has several set methods that change its internal state and effect
a later call, so it is useless to make it thread safe. So I do not think we need to add a
javadoc to tell users it is not thread safe.


> Make AsyncTable thread safe
> ---------------------------
>                 Key: HBASE-17372
>                 URL: https://issues.apache.org/jira/browse/HBASE-17372
>             Project: HBase
>          Issue Type: Sub-task
>          Components: asyncclient, Client
>    Affects Versions: 2.0.0
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>             Fix For: 2.0.0
>         Attachments: HBASE-17372.patch, HBASE-17372-v1.patch, HBASE-17372-v2.patch, HBASE-17372-v3.patch,
HBASE-17372-v4.patch, HBASE-17372-v5.patch, HBASE-17372-v6.patch
> The most methods are already thread safe. The problem is that we have some methods that
used to set timeout, we need to remove these methods and add a parameter for each call to
specific timeout settings.

This message was sent by Atlassian JIRA

View raw message