[KULRICE-11657] Additive Database Structure: Adapt DevOps libraries to compensate Created: 17/Jan/14  Updated: 24/Sep/14  Resolved: 16/Jun/14

Status: Closed
Project: Kuali Rice Development
Component/s: Database
Affects Version/s: 2.4
Fix Version/s: 2.5
Security Level: Public (Public: Anyone can view)

Type: Improvement Priority: Major
Reporter: Kristina Taylor (Inactive) Assignee: Kristina Taylor (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 2 days
Original Estimate: 2 days
Environment:

The DevOps libraries need to be able to handle the new database format.


Epic Link: Additive Database
Sprint: Core 2.5.0-m4 Sprint 1
KAI Review Status: Not Required
KTI Review Status: Not Required
Code Review Status: Not Required
Include in Release Notes?:
Yes

 Description   

The current DevOps libraries are not designed to handle Rice's new additive data structure. They need to be adapted to do this and the old method needs to be deprecated.



 Comments   
Comment by Kristina Taylor (Inactive) [ 16/Jun/14 ]

Determined that it is optional to have the DevOps libraries changed since I changed them a lot in the last iteration. There are two candidates to put in kuali-util though:

org.kuali.rice.db.config.profile.MetaInfDataLocationProfileConfig
org.kuali.rice.db.config.profile.MetaInfDAtaTypeProfileConfig

They are currently checked in to the project and moving them will be considered in the code cleanup.

Generated at Fri Mar 05 22:08:54 CST 2021 using JIRA 7.0.11#70121-sha1:19d24976997c1d95f06f3e327e087be0b71f28d4.