Return-Path: 
 <user-return-34463-apmail-hbase-user-archive=hbase.apache.org@hbase.apache.org>
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 58F30E1DD
	for <apmail-hbase-user-archive@www.apache.org>;
 Thu, 28 Feb 2013 06:31:12 +0000 (UTC)
Received: (qmail 75540 invoked by uid 500); 28 Feb 2013 06:31:10 -0000
Delivered-To: apmail-hbase-user-archive@hbase.apache.org
Received: (qmail 74549 invoked by uid 500); 28 Feb 2013 06:31:09 -0000
Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hbase.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hbase.apache.org>
List-Post: <mailto:user@hbase.apache.org>
List-Id: <user.hbase.apache.org>
Reply-To: user@hbase.apache.org
Delivered-To: mailing list user@hbase.apache.org
Delivered-To: moderator for user@hbase.apache.org
Received: (qmail 76619 invoked by uid 99); 28 Feb 2013 05:56:17 -0000
X-ASF-Spam-Status: No, hits=3.1 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,SUBJ_ALL_CAPS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of
 chaitanyaeswar.chaitanya@gmail.com designates 209.85.210.177 as permitted
 sender)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:x-received:date:message-id:subject:from:to
         :content-type;
        bh=BO7R4/f2m29D6lAsa1OpuI/iWZJsPih3wO3fvUq3Cp0=;
        b=wmp/UGJaTs6nCNgX7hbkRLpz1PlAzAztNlX4nVoY1X6i2hCZ7Gv8XnBAmfI2MMDjtX
         1zLpdZYlOWfpski2DBg3BMNNQLiZwG28a0X3iukzNH0VeTe2D6ruGVsx4fbZDbxJUZBV
         BkvbLb7xGwTJWjYDtjjJL1fDC80UQx6hi04mMqH/6xy1XEOs0zLRybWEaEau8upjhId2
         edVmf1So14bo12Sr343whlD9O6e3k+RtRmd7+uuHHNXHCxpw9D3lagHrVEa4zxCUgInE
         E+GTvU/I01baKawpQv2t97AlAdvYESQaJo2LhRYuxXJSa15QCkMKiuv3TVmGIsqdi0bm
         LVrQ==
MIME-Version: 1.0
X-Received: by 10.50.160.201 with SMTP id xm9mr2650747igb.101.1362030948162;
 Wed, 27 Feb 2013 21:55:48 -0800 (PST)
Date: Thu, 28 Feb 2013 11:25:48 +0530
Message-ID: 
 <CAKLut_SStngGpniJMB-Rsc4BRabL2Rx1FEB_JSr=5y9XBO9UMQ@mail.gmail.com>
Subject: LIMITATIONS OF CODE THAT CAN BE WRITTEN IN HBASE COPROCESSORS
From: chaitanya eswar <chaitanyaeswar.chaitanya@gmail.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=14dae9340ea9d6a26704d6c28a8b
X-Virus-Checked: Checked by ClamAV on apache.org

--14dae9340ea9d6a26704d6c28a8b
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I am trying to  do this,
When a put is done in one table  i have to store those puts using a static
variable in coprocessor and whenever client issues flush i have to update
the other table.
When i try to do something new coprocessor isn't getting deployed and
sometimes even the master isn't getting started.
I wish to know whether there are any limitations to functionality of
coprocessors

--14dae9340ea9d6a26704d6c28a8b--