odpi/egeria-python

Stars
7
Rank 2,294,361 (Top 46 %)
Language
Python
License
Apache License 2.0
Created about 2 years ago
Updated 3 months ago

odpi/egeria-python

odpi

There are no reviews yet. Be the first to send feedback to the community and the maintainers!

Python library for Egeria

egeria

OpenDS4All

OpenDS4All project, hosted by LF AI & Data

data-governance

Egeria's Guidance on Governance as well as large media files such as presentations and movies

specs

ODPi specifications, developed by ODPi Runtime and ODPi Operations projects. Currently in Emeritus status

egeria-ui

User interface instance using main Egeria functionalities.

egeria-connector-ibm-information-server

IBM Information Server connectors for Egeria: repository proxy connector for IGC, data engine proxy connector for DataStage.

egeria-docs

Documentation repository for the Egeria project.

egeria-connector-hadoop-ecosystem

Hadoop ecosystem connectors for Egeria: repository proxy connector for Apache Atlas.

egeria-connector-sas-viya

Egeria connector for SAS Information Catalog

egeria-ui-components

Encapsulated reactjs components with business logic inside.

egeria-js-commons

Common module for storing static data such as key value objects, SVGs, icon mappings, API urls.

egeria-connector-xtdb

Pluggable repository for Egeria, using XTDB (formerly "Crux") as the back-end to natively support historical metadata.

egeria-database-connectors

Connectors for exchanging metadata

egeria-charts

Helm chart repository

egeria-react-ui

A multi-tenant, role based Egeria React UI for Open Metadata, that has eco-system and solutions capabilities.

egeria-samples

various samples that can be useful either for learning or as initial starting points for working with Egeria

egeria-api-mocks

Support for mocking Egeria API for UI dev test

happi-graph

Generic graph rendering solution.

egeria-samples-api

A collection of samples illustrating the different APIs of Egeria.

egeria-ui-core

Core library that includes generic reactjs components used across the user interface.

egeria-dev-projects

Fun projects for developers to help them learn about the Egeria technology

egeria-connector-hivemetastore

Egeria repository connector for Hive metastore. Initially targeted at spark metadata

egeria-k8s-operator

Egeria Kubernetes operator

egeria-connector-integration-topic-strimzi

Strimzi Egeria integration connector for Kafka Topics

egeria-coco-labs

Egeria Jupiter notebooks used in the Open Metadata Labs

Jupyter Notebook

egeria-palisade

egeria-connector-integration-event-schema

Provides an integration connector that extract event schemata from a schema registry (including Confluent schema registry). The connector will be a polling connector and will look in Egeria for new topics that if present in the confluent registry, the associate schema elements will be brought into Egeria.

egeria-connector-repository-file-sample

Provides a repository proxy sample that uses polling. The target is a file folder

self-certification-reports

Commit your ODPi spec test runs to this repo to let others know if your platform or application is ODPi compliant

egeria-template-newrepo

Template for new Egeria repository

tsc

ODPi TSC Materials, Guidelines, and Meeting notes

egeria-connector-omrs-caching

Provides an OMRS repository proxy connector that has an embedded repository that can be used to cache entities and relationships.

security-guide

OBAIC

ci-management

egeria-connector-integration-lineage-event-driven-sample

Sample showing how to bring lineage into Egeria

egeria-listener-hms

Provides a Hive Metastore listener to feed HMS changes into an Egeria ecosystem

bi-ai

ODPi BI and AI Project

egeria-cloudnative

Supports egeria cloud-native workgroup activities *currently prototyping only*

egeria-connector-jdbc

JDBC connectors for Egeria (Integration and Resource)

egeria-workspaces

Docker compose starter configurations for work, samples, and demos

Jupyter Notebook

egeria-dojo-developer

Provides the starting project structure for the developer dojo. The participant creates a clone of it and works from there - they do not merge their code back into the repository. There is also a branch which includes the sample answers that they can refer to if they get stuck.