Read from a database and import into Collibra

One of the more common integration patterns around the Collibra platform is to frequently import records from a database such as reference data, data quality results, inventory of technology assets and so on into Collibra. You would usually execute one or more SQL queries against the database. You would then map the result set to the Collibra metamodel and then import the data into Collibra. The goal of this Spring Boot-based integration template is to demonstrate how to implement such integration use cases using Collibra APIs. As a Collibra integration developer, you can use the code behind this integration template and several others to build your own custom integrations faster and using best practices.

This Spring Boot application creates and populates an in-memory database with meaningful records such as reference data and data quality results, which it imports into Collibra. The application also shows how you can map the result of any SQL query to the Collibra metamodel, whether it be the packaged one or metamodel elements specific to a particular implementation of the Collibra platform. This application focuses on the following types of records and how you can import them into Collibra but you can adapt the code to your own use cases:

1. Reference data from a database retrieved using SQL queries.
2. Data quality check results from a database retrieved using SQL queries.
3. Data from systems, applications and databases from a database retrieved using SQL queries.

Elements in Scope

The integration is designed to retrieve the following metadata:

Asset Type

• Code Set
• Code Value
• Data Quality Metric
• System
• Application
• Database

To receive support on this item, you can engage our Professional Services team or post any questions in the Data Citizens Community.