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 051C2FA66 for ; Fri, 3 May 2013 11:34:57 +0000 (UTC) Received: (qmail 3805 invoked by uid 500); 3 May 2013 11:34:55 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 3148 invoked by uid 500); 3 May 2013 11:34:50 -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 3115 invoked by uid 99); 3 May 2013 11:34:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 May 2013 11:34:49 +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 anoop.hbase@gmail.com designates 209.85.216.173 as permitted sender) Received: from [209.85.216.173] (HELO mail-qc0-f173.google.com) (209.85.216.173) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 May 2013 11:34:42 +0000 Received: by mail-qc0-f173.google.com with SMTP id h29so664376qcu.4 for ; Fri, 03 May 2013 04:34:22 -0700 (PDT) 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=3+MfbHJsWds4WfIiKIkbSwmiQ2L8BhIdydEBd718ha0=; b=HoMfnvlEtlU1FqAIOBuI0Qwp0iJb/YLLSGSRzEK24fR+5a0Vj77wrZ9swdMIurCj8A egsrTAt9rrjb71WO5fWqFQjG0i77DPouQoo+Wl+bvanUSJaYoKO7ZBSnbv5VsHJf2NgQ aLpTQ0TDlkjB0NydkyrbYGqU+ORKlnD3/GL/IIuOIa/5kr1cZ+fTD+rFXn4PywZpHFr0 /FBGCK/AjV4kPycwcqzimUm9CpIp8X859FLFVd72zLJjYvrML/z6bV5YtRSbWgGsi9Mj tCWIQhIbN7OIvDrccaCsQaQ3LdcqNKQQe7SGAPphRDX0d49mcPfWPluHZAAdWC8ckarh wA/A== MIME-Version: 1.0 X-Received: by 10.49.61.106 with SMTP id o10mr1625220qer.20.1367580861993; Fri, 03 May 2013 04:34:21 -0700 (PDT) Received: by 10.49.83.200 with HTTP; Fri, 3 May 2013 04:34:21 -0700 (PDT) In-Reply-To: References: Date: Fri, 3 May 2013 17:04:21 +0530 Message-ID: Subject: Re: Endpoint vs. Observer Coprocessors From: Anoop John To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=047d7bdc08cc7b356704dbcebb7a X-Virus-Checked: Checked by ClamAV on apache.org --047d7bdc08cc7b356704dbcebb7a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable >data in one common variable Didn't follow u completely. Can u tell us little more on your usage. How exactly the endpoint to be related with the CP hook (u said postPut) -Anoop- On Fri, May 3, 2013 at 4:04 PM, Pavel Han=C4=8Dar = wrote: > Hello, > I've just started to discover coprocessors. Namely the classes > BaseEndpointCoprocessor and BaseRegionObserver. I need the postPut() meth= od > and than some special user calls. So I need both, but I want to have my > data in one common variable. What's the easiest way to manage? Do I have = to > Implement my own Base...Coprocessor class? > Best wishes, > Pavel Han=C4=8Dar > --047d7bdc08cc7b356704dbcebb7a--