Skip to content
In development

A component that is in development means that the Egeria community is still building the function. The code is added continuously in small pieces to help the review and socialization process. It may not run, or do something useful - it only promises not to break other function. Expect to find git issues describing the end state.

PostgreSQL Repository Connector

Connector summary

The PostgreSQL OMRS Repository Connector provides a repository implementation that stores metadata in a PostgreSQL Database. Each Open Metadata Repository uses the same table structure within its own Database Schema. This database schema is managed by a single instance of the PostgreSQL Repository Connector.

Access to the PostgreSQL Database Schema is provided by the JDBC Resource Connector. This connector manages the SQL Queries, connection management and use of the secrets store for security connections.

The diagram below shows the tables used in the PostgreSQL Database Schema.

---
title: PostgreSQL Repository Database Schema
---

erDiagram

    classification ||--o{ classification_property_value : "has properties"
    classification }o--|| entity : "attached to entity"

    entity ||--o{ entity_property_value : "has properties"

    relationship ||--o{ relationship_property_value : "has properties"
    relationship }o--|| entity : end1
    relationship }o--|| entity : end2

Debugging

Logging levels can be set up in the application.properties file. To log each SQL command issues, add the following:

logging.level.org.odpi.openmetadata.adapters.connectors.resource.jdbc=DEBUG

To log how queries are built up from the values supplied on the repository API, add the following:

logging.level.org.odpi.openmetadata.adapters.repositoryservices.postgres.repositoryconnector.database=DEBUG

Raise an issue or comment below