phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Taylor <jamestay...@apache.org>
Subject Re: Phoenix coprocessor after migration to 3.0
Date Fri, 21 Mar 2014 01:54:17 GMT
Hi Sean,
There's a migration step you need to do, as we don't want to convert over
2.2.x tables unless you configure it as such. I'll write-up a page on our
website that explains the config param you need to set.

Unless you're just doing testing, please wait until we've officially
released to cut over to 3.0, though, as the schema may change as a result
of bugs/issues found during this voting phase.

Thanks,
James


On Thu, Mar 20, 2014 at 11:47 AM, Sean Huo <sean@crunchyroll.com> wrote:

> I have a table that was created with phoenix-2.* build.
> I have migrated the table to phoenix 3. However,
> I still see the old coprocessor references in the table,
> as in the following
>
> {NAME => 'BI.EVENTS', coprocessor$10 =>
> '|org.apache.hadoop.hbase.index.Indexer|1073741823|index.builder=org.apache.phoenix.index.PhoenixIndexBuilder,org.apache.hadoop.hbase.index.codec.class=org.apache.
> true
>
>
>  phoenix.index.PhoenixIndexCodec', coprocessor$9 =>
> '|org.apache.phoenix.coprocessor.ServerCachingEndpointImpl|1|',
> coprocessor$8 =>
> '|org.apache.phoenix.coprocessor.GroupedAggregateRegionObserver|1|', co
>
>
>
>  processor$7 =>
> '|org.apache.phoenix.coprocessor.UngroupedAggregateRegionObserver|1|',
> coprocessor$6 => '|org.apache.phoenix.coprocessor.ScanRegionObserver|1|',
> coprocessor$5 => '|com.salesforce.hbase.ind
>
>
>
>  ex.Indexer|1073741823|com.salesforce.hbase.index.codec.class=com.salesforce.phoenix.index.PhoenixIndexCodec,index.builder=com.salesforce.phoenix.index.PhoenixIndexBuilder',
> coprocessor$4 => '|com.salesfo
>
>
>  rce.phoenix.coprocessor.ServerCachingEndpointImpl|1|', coprocessor$3 =>
> '|com.salesforce.phoenix.coprocessor.GroupedAggregateRegionObserver|1|',
> coprocessor$2 => '|com.salesforce.phoenix.coprocessor.Ungr
>
>
>
>  oupedAggregateRegionObserver|1|', coprocessor$1 =>
> '|com.salesforce.phoenix.coprocessor.ScanRegionObserver|1|', FAMILIES =>
> [{NAME => 'EVENT', DATA_BLOCK_ENCODING => 'FAST_DIFF', BLOOMFILTER =>
> 'NONE', R
>
>
>  EPLICATION_SCOPE => '0', COMPRESSION => 'NONE', VERSIONS => '3', TTL =>
'
> 2147483647', MIN_VERSIONS => '0', KEEP_DELETED_CELLS => 'true', BLOCKSIZE
> => '65536', ENCODE_ON_DISK => 'true', IN_MEMORY => 'fals
>
>
>
>  e', BLOCKCACHE => 'true'}, {NAME => 'USER', DATA_BLOCK_ENCODING =>
> 'FAST_DIFF', BLOOMFILTER => 'NONE', REPLICATION_SCOPE => '0', COMPRESSION
> => 'NONE', VERSIONS => '3', TTL => '2147483647', MIN_VERSIONS
>
>
>
>  => '0', KEEP_DELETED_CELLS => 'true', BLOCKSIZE => '65536',
> ENCODE_ON_DISK => 'true', IN_MEMORY => 'false', BLOCKCACHE => 'true'}]}
>
>
> How do I get rid of all the com.salesforce.phoenix coprocessors?  This
> leads to tons of error messages during regionserver start up.
>
> Thanks
>
> Sean
>

Mime
View raw message