You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Karthik K <os...@gmail.com> on 2010/03/29 06:52:34 UTC
HTable - thread-safety
HTable is not thread-safe , as seen from the handling of internal data
structures, and is ok.
But put / delete seems to have sync. blocks though. any rationale about the
same ? would it be worth removing the 'sync' from on the methods ?
Re: HTable - thread-safety
Posted by Karthik K <os...@gmail.com>.
HBASE-2389 in place, for further discussion.
On Mon, Mar 29, 2010 at 9:33 AM, Jean-Daniel Cryans <jd...@apache.org>wrote:
> I think it's legacy (HTable has been around for a while), although it
> doesn't do any harm right? Feel free to open a jira (and even submit a
> patch :P ).
>
> J-D
>
> On Sun, Mar 28, 2010 at 9:52 PM, Karthik K <os...@gmail.com> wrote:
> > HTable is not thread-safe , as seen from the handling of internal data
> > structures, and is ok.
> >
> > But put / delete seems to have sync. blocks though. any rationale about
> the
> > same ? would it be worth removing the 'sync' from on the methods ?
> >
>
Re: HTable - thread-safety
Posted by Jean-Daniel Cryans <jd...@apache.org>.
I think it's legacy (HTable has been around for a while), although it
doesn't do any harm right? Feel free to open a jira (and even submit a
patch :P ).
J-D
On Sun, Mar 28, 2010 at 9:52 PM, Karthik K <os...@gmail.com> wrote:
> HTable is not thread-safe , as seen from the handling of internal data
> structures, and is ok.
>
> But put / delete seems to have sync. blocks though. any rationale about the
> same ? would it be worth removing the 'sync' from on the methods ?
>