Details

    • Type: Sub Task Sub Task
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.0, 2.0.1, 2.0.2, 2.1
    • Fix Version/s: 2.1.2
    • Component/s: Database, Packaging
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-7410Rice Upgrade scripts should not have "demo" or sample data or tables
      KULRICE-13474Validate that the Rice upgrade scripts execute and produce the correct final schema when run against the previous version of the database
      KULRICE-7448Database upgrade scripts should not drop tables
      KULRICE-10125Apply sampleApp data scripts
      KULRICE-6600Rice 2.0 upgrade scripts coming with KIM bootstrap data need to be consistent w.r.t ID generation
      KULRICE-7398Rice 2.1 Upgrade script recreates sequence
      KULRICE-11293MySQL scripts for 2.1.3 - 2.2.1 and 2.1 - 2.2 upgrade do not work
      KULRICE-10277Prepare database upgrade scripts for the 2.3.1 release
      KULRICE-9369Upgrade Script Error
      KULRICE-2621Remove old fields from data dictionary related to Document Type merge, KIM work, etc., create a script which will remove them from data dictionary files
    • Rice Module:
      KIM
    • Application Requirement:
      KFS
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      The rice upgrade scripts make an assumption about the data in various ID fields. In the KFS dataset and some implementor datasets, the ID attributes of various items are not numeric. The Rice upgrade script assumes numeric in certain places like:

      select (max(to_number(perm_id)) + 1) from krim_perm_t

      This causes all of the new KIM data items to blow up.

      The scripts need to be re-coded to use hard-coded alphanumeric identifiers. (KFS started using KFS as a mandatory prefix early last year for all new data so that there would be no chance of a collision with implementors or new Rice/KC data.)

      Additionally, the upgrade scripts need to contain pre-checks for problem data BEFORE running. I also ran into the problem that not all of the permission/responsibility names were unique before running the script. That caused a script failure. The upgrade script should fail to run if certain pre-conditions are not met until Rice changes to using a tool like Liquibase for their upgrades.

        Issue Links

          Activity

          Hide
          Shannon Hess added a comment - - edited

          Couple of questions about this -

          1. Which KFS and KC email lists should I use when I'm ready to send the email out asking people to test the scripts out?

          2. I don't see an upgrade script section in the current download page - http://site.kuali.org/rice/2.1.0/reference/html/portal.html . Is this something new that is going to be added to the next page, or is there a different downloads page?

          Show
          Shannon Hess added a comment - - edited Couple of questions about this - 1. Which KFS and KC email lists should I use when I'm ready to send the email out asking people to test the scripts out? 2. I don't see an upgrade script section in the current download page - http://site.kuali.org/rice/2.1.0/reference/html/portal.html . Is this something new that is going to be added to the next page, or is there a different downloads page?
          Hide
          Eric Westfall added a comment -

          1. I think you want to alert Muddu and Bryan Hutchinson on the KFS side. On the KC side, you will want to alert Gayathri. LMK if you don't have their emails.

          2. I will ask Jessica how we want to handle this. I think what we talked about was for them to be in a zip file up here: http://kuali.org/download

          So we can package up the zip once things are looking good.

          Show
          Eric Westfall added a comment - 1. I think you want to alert Muddu and Bryan Hutchinson on the KFS side. On the KC side, you will want to alert Gayathri. LMK if you don't have their emails. 2. I will ask Jessica how we want to handle this. I think what we talked about was for them to be in a zip file up here: http://kuali.org/download So we can package up the zip once things are looking good.
          Hide
          Shannon Hess added a comment - - edited

          The README files have been created.

          Link to readme file for 1.0.3 to 2.0.0 – https://svn.kuali.org/repos/rice/branches/rice-2.1/scripts/upgrades/1.0.3%20to%202.0.0/final/README.TXT
          Link to readme file for 2.0.0 to 2.1 – https://svn.kuali.org/repos/rice/branches/rice-2.1/scripts/upgrades/2.0.0%20to%202.1/final/README.TXT

          I sent an email to Muddu, Bryan Hutchinson, and Gayathri with the above information and asked them to do some verification on their side.

          After KFS and KC has a chance to test and and changes are made based on feekback, we can zip these files up and add them to the downloads page.

          Show
          Shannon Hess added a comment - - edited The README files have been created. Link to readme file for 1.0.3 to 2.0.0 – https://svn.kuali.org/repos/rice/branches/rice-2.1/scripts/upgrades/1.0.3%20to%202.0.0/final/README.TXT Link to readme file for 2.0.0 to 2.1 – https://svn.kuali.org/repos/rice/branches/rice-2.1/scripts/upgrades/2.0.0%20to%202.1/final/README.TXT I sent an email to Muddu, Bryan Hutchinson, and Gayathri with the above information and asked them to do some verification on their side. After KFS and KC has a chance to test and and changes are made based on feekback, we can zip these files up and add them to the downloads page.
          Hide
          Shannon Hess added a comment -

          Resolving this issue since it it complete and out for testing.

          Show
          Shannon Hess added a comment - Resolving this issue since it it complete and out for testing.
          Hide
          Jessica Coltrin (Inactive) added a comment -

          closing all 2.1.2 Jiras

          Show
          Jessica Coltrin (Inactive) added a comment - closing all 2.1.2 Jiras

            People

            • Assignee:
              Shannon Hess
              Reporter:
              Jonathan Keller
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 2 days
                2d
                Remaining:
                Remaining Estimate - 2 days
                2d
                Logged:
                Time Spent - Not Specified
                Not Specified

                  Structure Helper Panel