Details

    • Type: Epic Epic
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Complete
    • Affects Version/s: 2.4
    • Fix Version/s: 2.5
    • Component/s: Database
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Epic Name:
      Additive Database
    • Similar issues:
      KULRICE-11659Additive Database Structure: Testing and code cleanup
      KULRICE-11656Additive Database Structure: Split Up Impex Resources
      KULRICE-11657Additive Database Structure: Adapt DevOps libraries to compensate
      KULRICE-3413Add dataset packaging to the Rice packaging scripts
      KULRICE-11658Additive Database Structure: Adapt maven goals from impex project
      KULRICE-50Document the structure of all of our database components in the project
      KULRICE-12417Correct errors in the installation guide's "Building the Rice Database" section
      KULRICE-9179KRAD_MSG_T not in client dataset upgrade scripts
      KULRICE-2227Create the implementation of the KimPermission interface and link to database
      KULRICE-9001Rice 2.2.0 database upgrade scripts omitted 2.1.2 changes
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      Currently, we build a master database using scripts and then delete from the datasets to create the bootstrap dataset. Now that we have put in the initial structure to separate our data sets, we can switch to building the databases starting from bootstrap and adding from there.

        Issues in Epic

          Activity

          Hide
          Kristina Taylor (Inactive) added a comment -

          We should probably get to this sooner rather than later. It would require another release of the devops libraries, but the developer performing the changes can mostly test this locally themselves. It does require a bit of research to make sure we are doing this correctly, especially when it comes to making sure all of the datasets have the right hierarchy. As an initial mind dump, I believe the following is the correct order:

          upgrades/**/client/bootstrap
          upgrades/**/server/bootstrap
          upgrades/**/client/demo
          upgrades/**/server/demo
          upgrades/**/client/test
          upgrades/**/server/test
          

          where the first entry is the initial setup and the rest of the entries depend on the ones above them.

          Show
          Kristina Taylor (Inactive) added a comment - We should probably get to this sooner rather than later. It would require another release of the devops libraries, but the developer performing the changes can mostly test this locally themselves. It does require a bit of research to make sure we are doing this correctly, especially when it comes to making sure all of the datasets have the right hierarchy. As an initial mind dump, I believe the following is the correct order: upgrades/**/client/bootstrap upgrades/**/server/bootstrap upgrades/**/client/demo upgrades/**/server/demo upgrades/**/client/test upgrades/**/server/test where the first entry is the initial setup and the rest of the entries depend on the ones above them.
          Show
          Kristina Taylor (Inactive) added a comment - Added Google doc to track this proposal: https://docs.google.com/a/kuali.org/document/d/1LV2j-WkWdGM6R5ozfFzpiB64sp7AHvJx8TGzu50I2Yw/edit#
          Hide
          Peter Giles (Inactive) added a comment -

          One thing to note is that there may be some cleanup to the upgrade scripts that will be required, as some devs have been putting the same scripts in multiple locations under upgrades/

          Show
          Peter Giles (Inactive) added a comment - One thing to note is that there may be some cleanup to the upgrade scripts that will be required, as some devs have been putting the same scripts in multiple locations under upgrades/
          Hide
          Kristina Taylor (Inactive) added a comment -

          I will be using http://svn.kuali.org/repos/rice/sandbox/KULRICE-11623/ for the main Rice work.

          Show
          Kristina Taylor (Inactive) added a comment - I will be using http://svn.kuali.org/repos/rice/sandbox/KULRICE-11623/ for the main Rice work.

            People

            • Assignee:
              Unassigned
              Reporter:
              Kristina Taylor (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel