Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: error (nike.apache.org: local policy)
From: Tianying Chang <tichang@ebaysf.com>
To: "user@hbase.apache.org" <user@hbase.apache.org>
Subject: RE: deploy saleforce phoenix coprocessor to hbase/lib??
Thread-Topic: deploy saleforce phoenix coprocessor to hbase/lib??
Thread-Index: AQHOrn8bBIcBnE9CTkGpk9cTe93A3JnA3cfw
Date: Wed, 11 Sep 2013 18:37:35 +0000
Message-ID: 
 <45D4C96DB8C88D489A4C8014A13FDFA7094352CF@PHX-EXRDA-S51.corp.ebay.com>
References: 
 <45D4C96DB8C88D489A4C8014A13FDFA709434821@PHX-EXRDA-S51.corp.ebay.com>
 <7162017282836005839@unknownmsgid>
In-Reply-To: <7162017282836005839@unknownmsgid>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

James, thanks for the explain.

So my understanding is the Phoenix wraps around HBase client API to create =
a  Pheonix table. Within this wrapper, it will call a "alter table" with th=
e coprocessor when it create a phoenix table, right?=20

Also, do we need to restart RS after deploy the jar under hbase/lib? Our cu=
stomers said it has to. But I feel it is unnecessary and weird. Can you con=
firm?=20

Thanks
Tian-Ying=20

-----Original Message-----
From: James Taylor [mailto:jtaylor@salesforce.com]=20
Sent: Tuesday, September 10, 2013 4:40 PM
To: user@hbase.apache.org
Subject: Re: deploy saleforce phoenix coprocessor to hbase/lib??

When a table is created with Phoenix, its HBase table is configured with th=
e Phoenix coprocessors. We do not specify a jar path, so the Phoenix jar th=
at contains the coprocessor implementation classes must be on the classpath=
 of the region server.

In addition to coprocessors, Phoenix relies on custom filters which are als=
o in the Phoenix jar. In theory you could put the jar in HDFS, use the rela=
tively new HBase feature to load custom filters from HDFS, and issue alter =
table calls for existing Phoenix HBase tables to reconfigure the coprocesso=
rs. When new Phoenix tables are created, though, they wouldn't have this ja=
r path.

FYI, we're looking into modifying our install procedure to do the above (se=
e https://github.com/forcedotcom/phoenix/issues/216), if folks are interest=
ed in contributing.

Thanks,
James

On Sep 10, 2013, at 2:41 PM, Tianying Chang <tichang@ebaysf.com> wrote:

> Hi,
>
> Since this is not a hbase system level jar, instead, it is more like user=
 code, should we deploy it under hbase/lib?  It seems we can use "alter" to=
 add the coprocessor for a particular user table.  So I can put the jar fil=
e any place that is accessible, e.g. hdfs:/myPath?
>
> My customer said, there is no need to run 'aler' command. Instead, as lon=
g as I put the jar into hbase/lib, then when phoenix client make read call,=
 it will add the the coprocessor attr into that table being read. It is kin=
d of suspicious. Does the phoenix client call a "alter" under cover for the=
 client  already?
>
> Anyone knows about this?
>
> Thanks
> Tian-Ying