Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-11658

Additive Database Structure: Adapt maven goals from impex project

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Complete
    • Affects Version/s: 2.4
    • Fix Version/s: 2.5
    • Component/s: Database
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-11657Additive Database Structure: Adapt DevOps libraries to compensate
      KULRICE-11656Additive Database Structure: Split Up Impex Resources
      KULRICE-10742Failed to execute goal org.kuali.maven.plugins:sql-maven-plugin:
      KULRICE-9030Rice 2.2 branch impex export job is not working
      KULRICE-11623Implement additive dataset database structure
      KULRICE-11659Additive Database Structure: Testing and code cleanup
      KULRICE-50Document the structure of all of our database components in the project
      KULRICE-9994Maven execution error on db/sql
      KULRICE-4113Add regex jars to impex lib so maven can run impex properly
      KULRICE-5060Update master database from 1.1 to 2.0 and update impex
    • Sprint:
      Core 2.5.0-m4 Sprint 1, Core 2.5.0-m4 Sprint 2
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      The maven goals for the impex project already are split into the client/server and bootstrap/demo/test model, so this needs to be adapted for the sql and xml projects so theses goals can be run by the server.

        Activity

        Hide
        Kristina Taylor (Inactive) added a comment - - edited

        Some data issues that have come up. We need to leave them in 2.3.x data but should remove them in the future.

        1. There is a node (SELECT * FROM KREW_RTE_BRCH_PROTO_T WHERE BRCH_NM = "ApprovalBranch" AND RTE_BRCH_PROTO_ID = "2422") which technically should not be in the bootstrap data set, but because of the way that the cleanup script is written, it was added there. We never use RTE_BRCH_PROTO_ID in KREW_RTE_NODE_T.
        2. The demo script 2014-03-06--KULRICE-10809.sql was put in the wrong location. It should be in client. It will not affect our bootstrap data set, but we need to put in a correction script for that.
        3. There is an entry in KRIM_PERM_T in bootstrap (SELECT * FROM KRIM_PERM_T WHERE NMSPC_CD = "KR-RULE-TEST") that has a namespace that does not exist in the bootstrap database. This needs to be evaluated and fixed.
        4. All of the documents that are in KREW_DOC_HDR_T should be removed.
        5. The KRCR_CMPNT_SET_T and KRCR_DRVD_CMPNT_T content are auto generated on server startup. This data should be completely removed.
        6. The contents of KRIM_ENTITY_CACHE_T should be wiped as this is a cache.

        Additional data corrections:

        1. There was a spelling mistake (UPDATE KRIM_PERM_T SET NM = REPLACE(NM, 'Apprive', 'Approve' ) WHERE NM LIKE '%Apprive%') that was only found in the master data set. It seems to be fine for the bootstrap data set, so I have corrected it.
        2. Data in some of the client tables (DELETE FROM KRNS_MAINT_DOC_T, DELETE FROM KRNS_MAINT_LOCK_T, DELETE FROM KRNS_DOC_HDR_T) was not being cleared from the server side equivalent in the demo data. This was determined to be a mistake as the same data should appear in the same context for both client and server side tables.
        3. We really can never remove any entries from KREW_DOC_TYP_T. This is a historical record and eliminating any entries with CUR_IND = 0 was a mistake in the cleanup scripts. I added these back into the bootstrap data but no correction scripts are necessary as the affected documents have been reingested in later versions and thus the added entries are merely historical data. The same goes for any tables related to KREW_DOC_TYP_T and also for KRCR_STYLE_T.
        Show
        Kristina Taylor (Inactive) added a comment - - edited Some data issues that have come up. We need to leave them in 2.3.x data but should remove them in the future. There is a node (SELECT * FROM KREW_RTE_BRCH_PROTO_T WHERE BRCH_NM = "ApprovalBranch" AND RTE_BRCH_PROTO_ID = "2422") which technically should not be in the bootstrap data set, but because of the way that the cleanup script is written, it was added there. We never use RTE_BRCH_PROTO_ID in KREW_RTE_NODE_T. The demo script 2014-03-06-- KULRICE-10809 .sql was put in the wrong location. It should be in client. It will not affect our bootstrap data set, but we need to put in a correction script for that. There is an entry in KRIM_PERM_T in bootstrap (SELECT * FROM KRIM_PERM_T WHERE NMSPC_CD = "KR-RULE-TEST") that has a namespace that does not exist in the bootstrap database. This needs to be evaluated and fixed. All of the documents that are in KREW_DOC_HDR_T should be removed. The KRCR_CMPNT_SET_T and KRCR_DRVD_CMPNT_T content are auto generated on server startup. This data should be completely removed. The contents of KRIM_ENTITY_CACHE_T should be wiped as this is a cache. Additional data corrections: There was a spelling mistake (UPDATE KRIM_PERM_T SET NM = REPLACE(NM, 'Apprive', 'Approve' ) WHERE NM LIKE '%Apprive%') that was only found in the master data set. It seems to be fine for the bootstrap data set, so I have corrected it. Data in some of the client tables (DELETE FROM KRNS_MAINT_DOC_T, DELETE FROM KRNS_MAINT_LOCK_T, DELETE FROM KRNS_DOC_HDR_T) was not being cleared from the server side equivalent in the demo data. This was determined to be a mistake as the same data should appear in the same context for both client and server side tables. We really can never remove any entries from KREW_DOC_TYP_T. This is a historical record and eliminating any entries with CUR_IND = 0 was a mistake in the cleanup scripts. I added these back into the bootstrap data but no correction scripts are necessary as the affected documents have been reingested in later versions and thus the added entries are merely historical data. The same goes for any tables related to KREW_DOC_TYP_T and also for KRCR_STYLE_T.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 3 days
              3d
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 3 days
              3d

                Agile

                  Structure Helper Panel