Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 757487E8A for ; Wed, 20 Jul 2011 23:45:09 +0000 (UTC) Received: (qmail 30845 invoked by uid 500); 20 Jul 2011 23:45:08 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 30789 invoked by uid 500); 20 Jul 2011 23:45:07 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 30781 invoked by uid 99); 20 Jul 2011 23:45:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Jul 2011 23:45:07 +0000 X-ASF-Spam-Status: No, hits=3.2 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HK_RANDOM_ENVFROM,HK_RANDOM_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lrgdt29@gmail.com designates 209.85.220.169 as permitted sender) Received: from [209.85.220.169] (HELO mail-vx0-f169.google.com) (209.85.220.169) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Jul 2011 23:44:59 +0000 Received: by vxg38 with SMTP id 38so809131vxg.14 for ; Wed, 20 Jul 2011 16:44:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=88szI1dSheQRPMfodP0XHzr9dRkbO/63oyCVmifyYVs=; b=tNiO9lUTEj3DWmYlWW+K3NM++PkWguc3luvgwFGaj8+M/Lom1pudXg6F28VtuSoZMp CAdPhLO7xl/su/HvTlwVVUCgUkACoKsR+ANlqaHD7bwZqdpn6OflIzhnBuTWkmP1xubs DR4RgVG62lvDN9mqIpmnscu3jml4j5ASL4CMc= MIME-Version: 1.0 Received: by 10.52.90.8 with SMTP id bs8mr9888665vdb.491.1311205478782; Wed, 20 Jul 2011 16:44:38 -0700 (PDT) Received: by 10.220.164.195 with HTTP; Wed, 20 Jul 2011 16:44:38 -0700 (PDT) Date: Wed, 20 Jul 2011 16:44:38 -0700 Message-ID: Subject: thread safety of incrementColumnValue From: large data To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=20cf3071c73aca580404a888d057 X-Virus-Checked: Checked by ClamAV on apache.org --20cf3071c73aca580404a888d057 Content-Type: text/plain; charset=ISO-8859-1 I have an HTable instance instantiated as part of a singleton service. This singleton service is called from different threads from different parts of the app. Reading through the HTable docs suggests not to use single HTable instance for updates, if it's true how can incrementColumnValue provide thread safety? thanks --20cf3071c73aca580404a888d057--