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

Connector Category: Native Repository Connector
Hosting Service: Open Metadata Repository Services (OMRS)
Hosting Server: Metadata Access Store
Source Module: postgres-repository-connector
Jar File Name: postgres-repository-connector.jar
ConnectorProviderClassName: org.odpi.openmetadata.adapters.repositoryservices.inmemory.repositoryconnector/PostgresOMRSRepositoryConnectorProvider.java

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
    entity ||--o{ mapping_properties : "optional third party mapping"
    relationship ||--o{ mapping_properties : "optional third party mapping"
    entity |o--|| instance_properties : "entity properties"
    classification |o--|| instance_properties : "classification properties"
    relationship |o--|| instance_properties : "relationship properties"

    instance_properties ||--o{ instance_property_value : manages
    instance_property_value |o--o| instance_properties : "is collection to"

Raise an issue or comment below