During testing with GK data, Jakub noted that some of the additional fields failed to migrate due problems like null values. Testing found for almost 2000000 additional fields migrated, there were 120 broken ones.
How do we handle these failures - can cleanup and manual migration occur after upgrade? Do we create a validation script to be run prior to upgrade to determine if problems are coming?
We have made the following commits to handle broken additional fields:
Fix for null values in responses: ebb076e9db6a790d78ca71d02a73459975b298e5
Thanks Jakub. Couple of things I'd like to ask:
1. can you document where the QG log written by default, and the command you'd use to execute this parser for us to document in support/release notes.
2. Specific to GK, what is the query that should be used to find/fix the null prior to migration? I'd rather have GK fix their bad rows prior to migration if possible so that all additional fields work on first try in their test and production environments.
1. QG log simply is printed on stdout, so should be available in catalina.out. You have to trim this file to contain only messages printed during migration and run the following command:
awk -f qgmig_log_parser.awk catalina.out
2. You can find all NULL values using the following commands:
select * from customer_custom_field where FIELD_VALUE is NULL;
select * from account_custom_field where FIELD_VALUE is NULL;
select * from office_custom_field where FIELD_VALUE is NULL;
select * from personnel_custom_field where FIELD_VALUE is NULL;
You can fix those values using the following commands:
update customer_custom_field set FIELD_VALUE="" where FIELD_VALUE is NULL;
update account_custom_field set FIELD_VALUE="" where FIELD_VALUE is NULL;
update office_custom_field set FIELD_VALUE="" where FIELD_VALUE is NULL;
update personnel_custom_field set FIELD_VALUE="" where FIELD_VALUE is NULL;
can you put the git reference in this issue where we now will take care of these null values as part of migration?
Verified on 15.12.2010
Bug is fixed properly.
Build Number: hudson-head-1.7.x-370
Branch Name: origin/1.7.x