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 9812118A6F for ; Fri, 18 Mar 2016 10:16:53 +0000 (UTC) Received: (qmail 14703 invoked by uid 500); 18 Mar 2016 10:16:52 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 14639 invoked by uid 500); 18 Mar 2016 10:16:52 -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 14623 invoked by uid 99); 18 Mar 2016 10:16:51 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Mar 2016 10:16:51 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id DA88F180319 for ; Fri, 18 Mar 2016 10:16:50 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.28 X-Spam-Level: * X-Spam-Status: No, score=1.28 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=spaggiari-org.20150623.gappssmtp.com Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id s2x__LA2RBXa for ; Fri, 18 Mar 2016 10:16:49 +0000 (UTC) Received: from mail-qk0-f182.google.com (mail-qk0-f182.google.com [209.85.220.182]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id D879E5F1D5 for ; Fri, 18 Mar 2016 10:16:49 +0000 (UTC) Received: by mail-qk0-f182.google.com with SMTP id s5so46825047qkd.0 for ; Fri, 18 Mar 2016 03:16:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=spaggiari-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=5mJ+jYZbT0YXGCB8UiOQsDUjjTTpl+j33UxpCTpyJU8=; b=UdYCOlOXcZvLAOB72/cOyJNbCHaoZTyuFUji6WmDeG3P+RzBYenkVY5rg45RRwUNm3 awtbPHpsv7h8rKL9X6DeubE+HeZq9gE86iP0IGwtWZP7+dRQSWt4h8wmwNS/QoywJ43e JkazMs9qlrSiN8vWMSb5EmhsdjCAZ8boqDZygeprXueIk/2qD1XR1haB4DGeN0ryFN0N eKsHYM+piAFM/NdKnZhSxm91OQLS8p5ZA0BP+kImD24xw2Rxi5r0ppUeOmVQ8SkSTpuF 1S+kImwPtiWRgGnQvWmDGiX6iDJVxjlYH1ZxnlqrnYO2esgcw4HfU+FLSyXhC/rH5qUv SuwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=5mJ+jYZbT0YXGCB8UiOQsDUjjTTpl+j33UxpCTpyJU8=; b=EwqFvo9y+zzOW4ZrdOjoUTUqo7htqoEuIs/a2IkSSnBCg/ZJVdeC4+RzJ41WUxfeP8 VnHXt88MscOOAqp9+xFLZJrptdXnYskM+Lr0RirIljN3Lrw0a9Rn0cIjKkiF73C+0o+i g7ZSa2APjkcRGr9Zym7fKO+DFBuFzyDxsp7vV5pyGqH0zGTxPtx8jfVqPiyBwFNEW2QS 8aCS9Gc8UlWYK5UkFD9vBvSB6nAgpnsI8ziGu/hVJIWltwHj0CNR7Ldl/6L29O6hWcvv QVXAzmjpYg2/q/vQ0EL63P/QD1I3iYCaCtlXBsMEk2Mtjg6yTRCNG7a3CCumdwn+ASIX XiMw== X-Gm-Message-State: AD7BkJJFVmvpT4RrhTQnFPVTQv0Cj+Azkf8YNWn/2Ryk3HUbweGeT9oR9+yERjtdetqdclyHPC61BfNmHC234w== X-Received: by 10.55.80.86 with SMTP id e83mr20436532qkb.91.1458296209317; Fri, 18 Mar 2016 03:16:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.32.180 with HTTP; Fri, 18 Mar 2016 03:16:29 -0700 (PDT) In-Reply-To: References: From: Jean-Marc Spaggiari Date: Fri, 18 Mar 2016 06:16:29 -0400 Message-ID: Subject: Re: How to implement increment in an idempotent manner To: user Content-Type: multipart/alternative; boundary=001a114a6a9688c477052e500b8b --001a114a6a9688c477052e500b8b Content-Type: text/plain; charset=UTF-8 What's about the other option where each bolt increment it's own column and at theend ou aggregate those few columns together? 2016-03-18 6:14 GMT-04:00 Sreeram : > The incremented field is more like an amount field that will be storing the > aggregate amount. Since the field will be incremented concurrently by > multiple bolts running in parallel, storing the value before increment and > then doing a put in case of replay will not help. > > Reason to have this field is to pre-compute a certain aggregate amount and > materialize it in the Hbase table. > > On Fri, Mar 18, 2016 at 3:30 PM, Jean-Marc Spaggiari < > jean-marc@spaggiari.org> wrote: > > > At the beginning of your Storm bolt process can you not do a put of "0"? > So > > it start back from scratch? Or else you will need to query the value, and > > keep the value to put it back if you need to replay your bolt > > > > Other option is, you increment a specific difference column and at the > end > > if you are successful with your bolt you increment te initial column with > > the new total counter? > > > > JMS > > > > 2016-03-18 5:33 GMT-04:00 Sreeram : > > > > > Hi, > > > > > > I am looking for suggestions from community on implementing HBase > > > increment in a idempotent manner. > > > > > > My use case is a storm Hbase bolt that atomically increments a HBase > > > counter. Replay of the storm bolt results in a double increment. > > > > > > Any suggestion on the approach to be taken is welcome. > > > > > > Thank you. > > > > > > Regards, > > > Sreeram > > > > > > --001a114a6a9688c477052e500b8b--