[ 
http://mifosforge.jira.com/browse/MIFOS-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakub Sławiński updated MIFOS-4320:
-----------------------------------

    Description: 
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|http://mifos.git.sourceforge.net/git/gitweb.cgi?p=mifos/head&a=commit&h=ebb076e9db6a790d78ca71d02a73459975b298e5]

  was:
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?






> Need to handle additional fields that fail data migration
> ---------------------------------------------------------
>
>                 Key: MIFOS-4320
>                 URL: http://mifosforge.jira.com/browse/MIFOS-4320
>             Project: mifos
>          Issue Type: Bug
>          Components: QuestionGroups/Surveys/PPI
>    Affects Versions: Release E
>            Reporter: jbrewster
>            Assignee: Jakub Sławiński
>            Priority: Major
>             Fix For: Release E - Iteration 13, Release E
>
>         Attachments: qgmig_log_parser.awk
>
>
> 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|http://mifos.git.sourceforge.net/git/gitweb.cgi?p=mifos/head&a=commit&h=ebb076e9db6a790d78ca71d02a73459975b298e5]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues

Reply via email to