Re: Migrate data between 2.2 and 4.0

I'd recommend using the upgrade script documented here: http://phoenix.apache.org/upgrade_from_2_2.html Thanks, James On Mon, Jun 30, 2014 at 10:34 AM, Kristoffer Sjögren wrote: > Maybe this is a big no-no but if I try to update column_family in > system.catalog from '0' to '_0' i get an excepti

Re: Migrate data between 2.2 and 4.0

Maybe this is a big no-no but if I try to update column_family in system.catalog from '0' to '_0' i get an exception. upsert into system.catalog (TABLE_NAME, COLUMN_NAME, COLUMN_FAMILY) select TABLE_NAME, COLUMN_NAME, '_0' from system.catalog where table_name = 'T' AND COLUMN_NAME = 'V'; java.lan

Re: Migrate data between 2.2 and 4.0

Thanks, that's good to know. On Sun, Jun 29, 2014 at 10:20 AM, James Taylor wrote: > FWIW, the upgrade script does not touch your data - it only modifies > the metadata in your SYSTEM.CATALOG table. > > On Sun, Jun 29, 2014 at 10:18 AM, Kristoffer Sjögren > wrote: > > Thanks James for the clar

Re: Migrate data between 2.2 and 4.0

FWIW, the upgrade script does not touch your data - it only modifies the metadata in your SYSTEM.CATALOG table. On Sun, Jun 29, 2014 at 10:18 AM, Kristoffer Sjögren wrote: > Thanks James for the clarification. I haven't tried the upgrade procedure > yet. I just wanted to migrate our existing data

Re: Migrate data between 2.2 and 4.0

Thanks James for the clarification. I haven't tried the upgrade procedure yet. I just wanted to migrate our existing data first to CDH5 and try out a few things on HBase 0.96. On Sun, Jun 29, 2014 at 9:50 AM, James Taylor wrote: > The default column family (i.e. the name of the column family us

Re: Migrate data between 2.2 and 4.0

The default column family (i.e. the name of the column family used for your table when one is not explicitly specified) was changed from _0 to 0 between 2.2 and 3.0/4.0. You can override this in your CREATE TABLE statement through the DEFAULT_COLUMN_FAMILY property. The upgrade script modifies this

Re: Migrate data between 2.2 and 4.0

After copying data from column _0 to column 0 phoenix is able to read the data (didn't try the catalog trick). I suppose this is the way Phoenix does the upgrade internally also (move data between columns)? On Wed, Jun 25, 2014 at 9:48 PM, Jeffrey Zhong wrote: > > No, you have to create column f

Re: Migrate data between 2.2 and 4.0

No, you have to create column family name 0 and copy the data from column family "_0" to it or (personally I didn't try the following) you might able to change meta data in system.catalog to use column family "_0" instead. For normal upgrade, you should follow instructions at http://phoenix.apac

Re: Migrate data between 2.2 and 4.0

Yes, the import worked after creating the column family and I can see all the rows when doing scans. But I got nothing when using Phoenix 4.0 client, so after comparing old and new tables I saw that 4.0 tables have column family name 0 instead of _0. Now as far as I know there is no way to rename

Re: Migrate data between 2.2 and 4.0

You can try to use hbase shell to manually add "_0" column family into your destination hbase table. Phoenix 4.0 from Apache can't work on hbase0.96. You can check discussions in https://issues.apache.org/jira/browse/PHOENIX-848 to see if your hbase is good for phoenix 4.0. Thanks, -Jeffrey On

Migrate data between 2.2 and 4.0

Hi We're currently running Phoenix 2.2 on HBase 0.94 CDH 4.4 and slowly preparing to move to Phoenix 4 and HBase 0.96 CDH 5. For my first tests I wanted to simply copy data from 0.94 to 0.96, which works fine for regular hbase table using the following commands: $ hbase org.apache.hadoop.hbase.m