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 5A659E446 for ; Tue, 26 Feb 2013 05:29:01 +0000 (UTC) Received: (qmail 40508 invoked by uid 500); 26 Feb 2013 05:28:59 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 40424 invoked by uid 500); 26 Feb 2013 05:28:58 -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 40396 invoked by uid 99); 26 Feb 2013 05:28:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Feb 2013 05:28:57 +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 (nike.apache.org: domain of yuzhihong@gmail.com designates 209.85.160.170 as permitted sender) Received: from [209.85.160.170] (HELO mail-gh0-f170.google.com) (209.85.160.170) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Feb 2013 05:28:50 +0000 Received: by mail-gh0-f170.google.com with SMTP id g14so644739ghb.1 for ; Mon, 25 Feb 2013 21:28:30 -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=yYnqGdHf9v8V+4yyDkhnL62KedhEY8XurSTV1+QZgdM=; b=wCedbcx9RJfY4qmbeC3yz2FPgK8+NykBRaGTXMa0vdf4L7CKJ9nSbDEA8Hc11bZmKm tp1z5gEq/eW3psOI1yqjkCew0wJP+fNac4D8SVG9ST/I2tUfwG6Hh1dfqjnzOk1THvcj mrJPBdpvjnR7e++QxqwAPG6WYbw+ZSM6fdiKU/MXG7b6tCXtMdgmNoU98hpg3+DcsfH1 bpH6KnZzl5pT7HV6GIwmG6uOJSpLuV9Ju77jNff2uXXKrR2JqGbO96ZDzhilnB28jV0O ua+TDJG2TkudDGBMOIdts13Pu1jsY8RCwNRz9ZmX/TxNVnOsJgbOeUcH1eFthJjXaiNk +J3Q== MIME-Version: 1.0 X-Received: by 10.236.86.200 with SMTP id w48mr22955478yhe.5.1361856509909; Mon, 25 Feb 2013 21:28:29 -0800 (PST) Received: by 10.101.208.18 with HTTP; Mon, 25 Feb 2013 21:28:29 -0800 (PST) In-Reply-To: References: <1358994226.69218.YahooMailNeo@web140602.mail.bf1.yahoo.com> Date: Mon, 25 Feb 2013 21:28:29 -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=20cf301af83f82520804d699eda8 X-Virus-Checked: Checked by ClamAV on apache.org --20cf301af83f82520804d699eda8 Content-Type: text/plain; charset=ISO-8859-1 In HBASE-7900, 'Have client Mutations (Put/Delete/etc.) and Result implement CellScanner Interface', Increment extends Mutation. Meaning Increment.getFamilyMap() method signature in 0.96 would change. Cheers 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. > > > --20cf301af83f82520804d699eda8--