[ 
https://issues.apache.org/jira/browse/PHOENIX-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942948#comment-13942948
 ] 

yang ming edited comment on PHOENIX-884 at 3/21/14 10:58 AM:
-------------------------------------------------------------

[~jamestaylor],I have tried to migrate table from 2.2.0 to 3.0.0.
hbase shell
Step1:
alter 'YK.VIDEO_QUOTESOURCE', METHOD => 'table_att_unset',NAME 
=>'coprocessor$1'...
step2:
alter 'YK.VIDEO_QUOTESOURCE', {METHOD => 'table_att', 'coprocessor' => 
'|org.apache.phoenix.coprocessor.ScanRegionObserver|1|'}

But I found another problem,the default cf has been changed('__0' to '0'),now 
in version 3.0.0 user-defined cf can not contain '_',is there other way to 
solve this problem?
I have created many tables in version 2.2.0,and the data size is 
large.Reimporting the data will waste a lot of time.



was (Author: yangming860101):
[~jamestaylor],I have tried to migrate table from 2.2.0 to 3.0.0.
hbase shell
Step1:
alter 'YK.VIDEO_QUOTESOURCE', METHOD => 'table_att_unset',NAME 
=>'coprocessor$1'...
step2:
alter 'YK.VIDEO_QUOTESOURCE', {METHOD => 'table_att', 'coprocessor' => 
'|org.apache.phoenix.coprocessor.ScanRegionObserver|1|'}

But I found another problem,the default cf has been changed('_0' to '0'),now in 
version 3.0.0 user-defined cf can not contain '_',is there other way to solve 
this problem?
I have created many tables in version 2.2.0,and the data size is 
large.Reimporting the data will waste a lot of time.


> How to migrate from 2.2.0 to 3.0.0
> ----------------------------------
>
>                 Key: PHOENIX-884
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-884
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: yang ming
>            Priority: Critical
>
> In my cluster there are many tables created by 2.2.0,but when doing system 
> upgrade I find the package structure of version 3.0.0 has been changed,so how 
> to migrate from 2.2.0 to 3.0.0?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to