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 94185E550 for ; Sat, 26 Jan 2013 00:39:30 +0000 (UTC) Received: (qmail 86085 invoked by uid 500); 26 Jan 2013 00:39:28 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 86044 invoked by uid 500); 26 Jan 2013 00:39:28 -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 86035 invoked by uid 99); 26 Jan 2013 00:39:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Jan 2013 00:39:28 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yuzhihong@gmail.com designates 209.85.217.176 as permitted sender) Received: from [209.85.217.176] (HELO mail-lb0-f176.google.com) (209.85.217.176) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Jan 2013 00:39:23 +0000 Received: by mail-lb0-f176.google.com with SMTP id s4so1614517lbc.7 for ; Fri, 25 Jan 2013 16:39:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=lThrS/N4vXdHsUDfb8zzVttWxc3MZcCQkAp197V6ha4=; b=bN569SZT7MQnC7Ibokk7aDECeuthQusTehc9PWY0evi3s6k2R8JEHr1psQ32v6GIv8 AeHI7x1bzTmuhYOTHI4C1yU40wfG9ju7YKgi9fx77kbHGLOVEgh4v/vVjDJ30aHxbO1F X9nb2/0sDckDgFR+P9FCkgGx5lZ5KRLtmv+9Mr6FbNTcE5AIZq0xjTF3UHodlJIB9bnw hliAnu0d0cFFcKNtmkRuKkkrHG6Yjw1rEPt5hr7B2yKMkPLGzoltOelKFBsH+2rIid4X SL1He+xHAtYhh3SRLt37okNvY9BNIh4KsN28S/dcE8T0y+Iz2tlH4PMwkWGRAQ/nLmM+ HrjQ== MIME-Version: 1.0 X-Received: by 10.152.112.36 with SMTP id in4mr6731648lab.35.1359160741713; Fri, 25 Jan 2013 16:39:01 -0800 (PST) Received: by 10.112.26.163 with HTTP; Fri, 25 Jan 2013 16:39:01 -0800 (PST) In-Reply-To: References: <1358994226.69218.YahooMailNeo@web140602.mail.bf1.yahoo.com> Date: Fri, 25 Jan 2013 16:39:01 -0800 Message-ID: Subject: Re: HBASE-7114 Increment does not extend Mutation but probably should From: Ted Yu To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=f46d0408d6d933d4f504d42645c5 X-Virus-Checked: Checked by ClamAV on apache.org --f46d0408d6d933d4f504d42645c5 Content-Type: text/plain; charset=ISO-8859-1 Amit: Can you tell us what operation you perform on the returned family map ? Thanks On Thu, Jan 24, 2013 at 3:37 AM, Amit Sela wrote: > I'm using Increment.getFamilyMap in a postIncrement Observer. > I'm running with HBase 0.94.2. > > Amit. > > On Thu, Jan 24, 2013 at 4:23 AM, lars hofhansl wrote: > > > The reason was that Increment was serialized differently (compared to all > > other mutations). > > In trunk that is no longer an issue, since the serialization logic is no > > longer part of the object to be serialized. > > > > > > -- Lars > > > > > > > > ________________________________ > > From: Ted Yu > > To: dev@hbase.apache.org; user@hbase.apache.org > > Sent: Wednesday, January 23, 2013 10:25 AM > > Subject: HBASE-7114 Increment does not extend Mutation but probably > should > > > > Hi, > > I want to get opinion on whether we should proceed with HBASE-7114 > > 'Increment does not extend Mutation but probably should' in trunk. > > > > Is anyone using Increment.setWriteToWAL or Increment.getFamilyMap ? > > For Increment.setWriteToWAL, are you using the Increment returned ? > > > > Your feedback would be appreciated. > > > --f46d0408d6d933d4f504d42645c5--