Class MigrationUtil
java.lang.Object
org.openmetadata.service.migration.utils.v120.MigrationUtil
-
Method Summary
Modifier and TypeMethodDescriptionstatic voidaddQueryService(org.jdbi.v3.core.Handle handle, CollectionDAO collectionDAO) Queries have a `queryUsedIn` field as a list of EntityRef.static voidupdateGlossaryAndGlossaryTermRelations(org.jdbi.v3.core.Handle handle, CollectionDAO collectionDAO) Before Release 1.2, Glossary and all the Glossary terms , even the deeply nested glossary terms have contains relation with Glossary and also its parent GlossaryTerm.
-
Method Details
-
addQueryService
Queries have a `queryUsedIn` field as a list of EntityRef. We'll pick up the first element of the list, since the tables should normally be in the same service, and: 1. Get the table from the ID 2. Identify the service 3. Update the Query.service EntityRef -
updateGlossaryAndGlossaryTermRelations
public static void updateGlossaryAndGlossaryTermRelations(org.jdbi.v3.core.Handle handle, CollectionDAO collectionDAO) Before Release 1.2, Glossary and all the Glossary terms , even the deeply nested glossary terms have contains relation with Glossary and also its parent GlossaryTerm. These causes delete issue as we recursively delete the GlossaryTerms When Glossary gets deleted. We have updated the Glossary -> nested GlossaryTerm to be "Has". This migration does following update 1. List all GlossaryTerms, update the status to Accepted , since we introduced the Glossary Approval Workflow 2. For each term we look at who is the parent is, There should be only one parent in 1.2.0 release, previous releases nested terms will have a two parents the parent GlossaryTerm and its Glossary. We will update the relation to Glossary to be "Has".
-