phoenix coprocessor to hbase/lib??
When a table is created with Phoenix, its HBase table is configured with the
Phoenix coprocessors. We do not specify a jar path, so the Phoenix jar that
contains the coprocessor implementation classes must be on the classpath of the
region server.
In addition
phoenix coprocessor to hbase/lib??
When a table is created with Phoenix, its HBase table is configured with
the Phoenix coprocessors. We do not specify a jar path, so the Phoenix jar
that contains the coprocessor implementation classes must be on the
classpath of the region server.
In addition
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 file any place
that is accessible, e.g. hdfs:/myPath?
My customer
When a table is created with Phoenix, its HBase table is configured
with the Phoenix coprocessors. We do not specify a jar path, so the
Phoenix jar that contains the coprocessor implementation classes must
be on the classpath of the region server.
In addition to coprocessors, Phoenix relies on
