Return-Path: Delivered-To: apmail-hadoop-hbase-dev-archive@minotaur.apache.org Received: (qmail 35084 invoked from network); 29 Mar 2010 16:34:03 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 29 Mar 2010 16:34:03 -0000 Received: (qmail 58900 invoked by uid 500); 29 Mar 2010 16:34:03 -0000 Delivered-To: apmail-hadoop-hbase-dev-archive@hadoop.apache.org Received: (qmail 58868 invoked by uid 500); 29 Mar 2010 16:34:03 -0000 Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-dev@hadoop.apache.org Delivered-To: mailing list hbase-dev@hadoop.apache.org Received: (qmail 58860 invoked by uid 99); 29 Mar 2010 16:34:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Mar 2010 16:34:03 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jdcryans@gmail.com designates 209.85.160.176 as permitted sender) Received: from [209.85.160.176] (HELO mail-gy0-f176.google.com) (209.85.160.176) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Mar 2010 16:33:55 +0000 Received: by gyd8 with SMTP id 8so5832648gyd.35 for ; Mon, 29 Mar 2010 09:33:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:received:message-id:subject :from:to:content-type:content-transfer-encoding; bh=4QsAouiYg9S61eVKfYLBEMtW6keZ1C93MiG3m6Y5xt8=; b=tWqgTaThC1N5oMxnKho7loY7jiicRmdVUZP757MttIbr6S57XF8fyvw0RLMs+19SJa TKAy/fpTWqRFqtFJ8GAf4Z10KKaAIeyCm5YLEPvQcfcE/UJgYqEabPmE6E59NQrxiNH/ 18alWAPmkoX/yS5oBXCXyeag0C+dpV7HIV36Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=bQLeIUki525SbjbcQNLG9rXqZmCXxR1f/laOaifhgd7Dt9Cbr5j3NGjNdT8aYwplG1 kzQkv3vkHrrKngIUVHoozyx0k8x5N6T1Erm+yfcbLgHVSCJXtEAEHQwvSrf+IqSOSceZ v4Gw83znpa8t8ENE0Gm+5iB1ROyVyMazwzbDQ= MIME-Version: 1.0 Sender: jdcryans@gmail.com Received: by 10.90.69.16 with HTTP; Mon, 29 Mar 2010 09:33:34 -0700 (PDT) In-Reply-To: References: Date: Mon, 29 Mar 2010 09:33:34 -0700 X-Google-Sender-Auth: 34cb05cefa956752 Received: by 10.90.58.32 with SMTP id g32mr4188953aga.120.1269880414717; Mon, 29 Mar 2010 09:33:34 -0700 (PDT) Message-ID: <31a243e71003290933q553f03b9mc62f44ec8a895173@mail.gmail.com> Subject: Re: HTable - thread-safety From: Jean-Daniel Cryans To: hbase-dev@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on 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 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 t= he > same =A0? would it be worth removing the 'sync' from on the methods ? >