Merge pull request #8376 from mandy-chessell/oak2024

Fix server operations client

CODEOWNERS

@@ -17,40 +17,32 @@ open-metadata-distribution/ @mandy-chessell
 open-metadata-implementation/ @mandy-chessell
 
 open-metadata-implementation/access-services/ @mandy-chessell
-open-metadata-implementation/access-services/asset-catalog/ @alexandra-bucur @lcpopa
 open-metadata-implementation/access-services/asset-consumer/ @mandy-chessell
-open-metadata-implementation/access-services/asset-lineage/ @lcpopa @popa-raluca 
 open-metadata-implementation/access-services/asset-manager/ @mandy-chessell
 open-metadata-implementation/access-services/asset-owner/ @mandy-chessell
 open-metadata-implementation/access-services/community-profile/ @mandy-chessell
 open-metadata-implementation/access-services/data-manager/ @mandy-chessell
-open-metadata-implementation/access-services/data-engine/ @popa-raluca @lcpopa
 open-metadata-implementation/access-services/design-model/ @mandy-chessell
 open-metadata-implementation/access-services/digital-architecture/ @mandy-chessell
 open-metadata-implementation/access-services/digital-service/ @mandy-chessell
-open-metadata-implementation/access-services/discovery-engine/ @mandy-chessell
-open-metadata-implementation/access-services/glossary-view/ @lcpopa @marius-patrascu
 open-metadata-implementation/access-services/governance-engine/ @mandy-chessell
 open-metadata-implementation/access-services/governance-program/ @mandy-chessell
 open-metadata-implementation/access-services/it-infrastructure/ @mandy-chessell
 open-metadata-implementation/access-services/project-management/ @mandy-chessell
 open-metadata-implementation/access-services/security-manager/ @mandy-chessell
 open-metadata-implementation/access-services/software-developer/ @mandy-chessell
 open-metadata-implementation/access-services/stewardship-action/ @mandy-chessell
-open-metadata-implementation/access-services/subject-area/ @davidradl
 open-metadata-implementation/adapters/ @mandy-chessell
-open-metadata-implementation/adatpers/authentication-plugins/ @mandy-chessell
-open-metadata-implementation/adatpers/open-connectors/ @mandy-chessell
+open-metadata-implementation/adapters/authentication-plugins/ @mandy-chessell
+open-metadata-implementation/adapters/open-connectors/ @mandy-chessell
 open-metadata-implementation/adapters/open-connectors/rest-client-connectors/spring-rest-client-connector/ @mandy-chessell
 open-metadata-implementation/adapters/open-connectors/configuration-store-connectors/configuration-encrypted-file-store-connector/ @cmgrote
-open-metadata-implementation/adapters/open-connectors/lineage-warehouse-connectors/ @marius-patrascu @lcpopa
 open-metadata-implementation/adapters/open-connectors/repository-services-connectors/open-metadata-collection-store-connectors/graph-repository-connector/ @mandy-chessell
 open-metadata-implementation/admin-services/ @mandy-chessell
 open-metadata-implementation/common-services/ @mandy-chessell
 open-metadata-implementation/frameworks/ @mandy-chessell
 open-metadata-implementation/governance-servers/ @mandy-chessell
 open-metadata-implementation/governance-servers/data-engine-proxy-services/ @cmgrote @popa-raluca
-open-metadata-implementation/governance-servers/lineage-warehouse-services/ @marius-patrascu @popa-raluca
 open-metadata-implementation/platform-services/ @mandy-chessell
 open-metadata-implementation/platform-chassis/ @mandy-chessell
 open-metadata-implementation/platform-chassis/platform-chassis-spring/ @bogdan-sava @lpalashevski

Content-Organization.md

@@ -18,28 +18,22 @@ The Egeria core repository contains the core Egeria functionality, and is organi
 * **[open-metadata-implementation](open-metadata-implementation)** - implementation of standards, frameworks and connectors.
 
   * **[access-services](open-metadata-implementation/access-services)** - domain specific APIs known as the Open Metadata Access Services (OMAS).
-    * **[asset-catalog](open-metadata-implementation/access-services/asset-catalog)** - search for assets.
     * **[asset-consumer](open-metadata-implementation/access-services/asset-consumer)** - create connectors to access assets.
-    * **[asset-lineage](open-metadata-implementation/access-services/asset-lineage)** - provide lineage reporting.
     * **[asset-manager](open-metadata-implementation/access-services/asset-manager)** - provide a synchronization interface for asset managers and catalogs.
     * **[asset-owner](open-metadata-implementation/access-services/asset-owner)** - manage metadata and feedback for owned assets.
     * **[community-profile](open-metadata-implementation/access-services/community-profile)** - manage personal profiles and communities.
-    * **[data-engine](open-metadata-implementation/access-services/data-engine)** - exchange metadata with a data processing engine.
     * **[data-manager](open-metadata-implementation/access-services/data-manager)** - exchange metadata with a technology that manages collections of data.
     * **[data-science](open-metadata-implementation/access-services/data-science)** - manage metadata for analytics.
     * **[design-model](open-metadata-implementation/access-services/design-model)** - manage content from design models.
     * **[digital-architecture](open-metadata-implementation/access-services/digital-architecture)** - support the definition of data standards and models.
     * **[digital-service](open-metadata-implementation/access-services/digital-service)** - manage metadata for a Digital Service.
-    * **[discovery-engine](open-metadata-implementation/access-services/discovery-engine)** - manage metadata for metadata discovery services.
-    * **[glossary-view](open-metadata-implementation/access-services/glossary-view)** - search for glossary content.
     * **[governance-engine](open-metadata-implementation/access-services/governance-engine)** - manage metadata for an operational governance engine.
     * **[governance-program](open-metadata-implementation/access-services/governance-program)** - set up and manage a governance program.
     * **[it-infrastructure](open-metadata-implementation/access-services/it-infrastructure)** - manage metadata about deployed infrastructure.
     * **[project-management](open-metadata-implementation/access-services/project-management)** - manage definitions of projects for metadata management and governance.
     * **[security-manager](open-metadata-implementation/access-services/security-manager)** - synchronization of metadata with security services.
     * **[software-developer](open-metadata-implementation/access-services/software-developer)** - deliver useful metadata to software developers.
     * **[stewardship-action](open-metadata-implementation/access-services/stewardship-action)** - manage metadata as part of a data steward's work to improve the data landscape.
-    * **[subject-area](open-metadata-implementation/access-services/subject-area)** - develop a definition of a subject area including glossary terms, reference data and rules.
 
   * **[adapters](open-metadata-implementation/adapters)** - pluggable component implementations.
     * **[authentication-plugins](open-metadata-implementation/adapters/authentication-plugins)** support extensions to technology such as LDAP that are used to verify the identity of an individual or service requesting access to data/metadata.
@@ -51,7 +45,6 @@ The Egeria core repository contains the core Egeria functionality, and is organi
       * **[dynamic-archiver-connectors](open-metadata-implementation/adapters/open-connectors/dynamic-archiver-connectors)** contains dynamic archiver services implementations.
       * **[event-bus-connectors](open-metadata-implementation/adapters/open-connectors/event-bus-connectors)** supports different event/messaging infrastructures.  They can be plugged into the topic connectors from the access-service-connectors and repository-service-connectors.
       * **[governance-action-connectors](open-metadata-implementation/adapters/open-connectors/governance-action-connectors)** contains GAF governance action implementations.
-      * **[lineage-warehouse-connectors](open-metadata-implementation/adapters/open-connectors/lineage-warehouse-connectors)** contains connectors for the lineage warehouse servers that maintain stores of optimized lineage information.
       * **[integration-connectors](open-metadata-implementation/adapters/open-connectors/integration-connectors)** contains connectors synchronously exchanging between different third party technologies.
       * **[repository-services-connectors](open-metadata-implementation/adapters/open-connectors/repository-services-connectors)** contains connector implementations for each type of connector supported by the Open Metadata Repository Services (OMRS).
         * **[audit-log-connectors](open-metadata-implementation/adapters/open-connectors/repository-services-connectors/audit-log-connectors)** supports different destinations for audit log messages.
@@ -76,7 +69,7 @@ The Egeria core repository contains the core Egeria functionality, and is organi
     * **[repository-handler](open-metadata-implementation/common-services/repository-handler)** - provides an enhanced set of services for accessing metadata from the [repository services](open-metadata-implementation/repository-services).
 
   * **[engine-services](open-metadata-implementation/engine-services)** - services that host data management and governance engines.  These run in the [Engine Host](https://egeria-project.org/concepts/engine-host) OMAG Server.
-    * **[asset-analysis](open-metadata-implementation/engine-services/asset-analysis)** - services that host [Open Discovery Framework (ODF)](open-metadata-implementation/frameworks/open-discovery-framework) discovery services.
+    * **[survey-action](open-metadata-implementation/engine-services/survey-action)** - services that host [Survey Action Framework (SAF)](open-metadata-implementation/frameworks/survey-action-framework) services.
     * **[repository-governance](open-metadata-implementation/engine-services/repository-governance)** - services that host dynamic governance services for open metadata repositories.
     * **[governance-action](open-metadata-implementation/engine-services/governance-action)** - services that host [Governance Action Framework (GAF)](open-metadata-implementation/frameworks/governance-action-framework) governance action services.
 
@@ -92,11 +85,9 @@ The Egeria core repository contains the core Egeria functionality, and is organi
     * **[gaf-metadata-management](open-metadata-implementation/framework-services/gaf-metadata-management)** - provides metadata management for the [Governance Action Framework (GAF)](open-metadata-implementation/frameworks/governance-action-framework) properties and APIs.
 
 * **[governance-servers](open-metadata-implementation/governance-servers)** - servers and daemons to run open metadata and governance function.
-    * **[data-engine-proxy-services](open-metadata-implementation/governance-servers/data-engine-proxy-services)** - supports automated metadata cataloguing from data engines.
     * **[engine-host-services](open-metadata-implementation/governance-servers/engine-host-services)** - supports the core function of the [Engine Host](https://egeria-project.org/concepts/engine-host) OMAG Server.
     * **[integration-daemon-services](open-metadata-implementation/governance-servers/integration-daemon-services)** - supports the core function of the [Integration Daemon](https://egeria-project.org/concepts/integration-daemon) OMAG Server.
-    * **[lineage-warehouse-services](open-metadata-implementation/governance-servers/lineage-warehouse-services)** - provides historic warehouse for lineage.
-
+
   * **[integration-services](open-metadata-implementation/integration-services)** - services that host integration connectors.  These run in the [Integration Daemon](https://egeria-project.org/concepts/integration-daemon) OMAG Server.
     * **[analytics-integrator](open-metadata-implementation/integration-services/analytics-integrator)** - services to catalog analytics services.
     * **[api-integrator](open-metadata-implementation/integration-services/api-integrator)** - services to catalog APIs supported by API Managers.

content-packs/README.md

@@ -1,5 +1,5 @@
 <!-- SPDX-License-Identifier: CC-BY-4.0 -->
-<!-- Copyright Contributors to the ODPi Egeria project 2020. -->
+<!-- Copyright Contributors to the ODPi Egeria project 2024. -->
 
 # Egeria Content Packs
 

open-metadata-distribution/omag-server-platform/build.gradle

@@ -46,7 +46,6 @@ dependencies {
     implementation project(':open-metadata-implementation:adapters:open-connectors:governance-action-connectors')
     implementation project(':open-metadata-implementation:adapters:open-connectors:event-bus-connectors:open-metadata-topic-connectors:inmemory-open-metadata-topic-connector')
     implementation project(':open-metadata-implementation:adapters:open-connectors:event-bus-connectors:open-metadata-topic-connectors:kafka-open-metadata-topic-connector')
-    implementation project(':open-metadata-implementation:adapters:open-connectors:lineage-warehouse-connectors:lineage-warehouse-janus-connector')
     implementation project(':open-metadata-implementation:adapters:open-connectors:repository-services-connectors:open-metadata-archive-connectors:open-metadata-archive-file-connector')
     implementation project(':open-metadata-implementation:adapters:open-connectors:repository-services-connectors:open-metadata-archive-connectors:open-metadata-archive-directory-connector')
     implementation project(':open-metadata-implementation:adapters:open-connectors:rest-client-connectors:spring-rest-client-connector')
@@ -57,7 +56,6 @@ dependencies {
     implementation project(':open-metadata-implementation:adapters:open-connectors:data-manager-connectors:unity-catalog-connectors')
     implementation project(':open-metadata-implementation:adapters:open-connectors:secrets-store-connectors:env-variable-secrets-store-connector')
     implementation project(':open-metadata-implementation:access-services:asset-consumer:asset-consumer-client')
-    implementation project(':open-metadata-implementation:access-services:asset-lineage:asset-lineage-client')
     implementation project(':open-metadata-implementation:access-services:asset-manager:asset-manager-client')
     implementation project(':open-metadata-implementation:access-services:asset-owner:asset-owner-client')
     implementation project(':open-metadata-implementation:access-services:it-infrastructure:it-infrastructure-client')
@@ -85,7 +83,6 @@ dependencies {
     implementation project(':open-metadata-implementation:integration-services:topic-integrator:topic-integrator-client')
     implementation project(':open-metadata-implementation:governance-server-services:engine-host-services:engine-host-services-client')
     implementation project(':open-metadata-implementation:governance-server-services:integration-daemon-services:integration-daemon-services-client')
-    implementation project(':open-metadata-implementation:governance-server-services:lineage-warehouse-services:lineage-warehouse-services-client')
     implementation project(':open-metadata-implementation:admin-services:admin-services-client')
     implementation project(':open-metadata-conformance-suite:open-metadata-conformance-suite-client')
     implementation project(':open-metadata-resources:open-metadata-samples:admin-services-samples:config-metadata-server-sample')
@@ -216,7 +213,6 @@ distributions {
                 from { project(':open-metadata-implementation:adapters:open-connectors:integration-connectors:openlineage-integration-connectors').jar }
                 from { project(':open-metadata-implementation:adapters:open-connectors:event-bus-connectors:open-metadata-topic-connectors:inmemory-open-metadata-topic-connector').jar }
                 from { project(':open-metadata-implementation:adapters:open-connectors:event-bus-connectors:open-metadata-topic-connectors:kafka-open-metadata-topic-connector').jar }
-                from { project(':open-metadata-implementation:adapters:open-connectors:lineage-warehouse-connectors:lineage-warehouse-janus-connector').jar }
                 from { project(':open-metadata-resources:open-metadata-samples:open-metadata-security-samples').jar }
                 from { project(':open-metadata-resources:open-metadata-samples:governance-action-samples').jar }
                 from { project(':open-metadata-implementation:adapters:open-connectors:rest-client-connectors:spring-rest-client-connector').jar }

open-metadata-implementation/access-services/README.md

@@ -14,12 +14,6 @@ The access services are as follows:
 functions such as analytics.  The Asset Consumer OMAS provides a factory function
 for the connectors, the ability to retrieve all the metadata about the asset and the ability to add feedback on the asset.
 
-* **[asset-lineage](asset-lineage)** - Track and publish lineage data.
-
-  The Asset Lineage OMAS listens to relevant lineage related events on the Enterprise topic level and publishes these on
-the Asset Lineage OutTopic, combined with relevant context information on the described entities. These events are 
-listened to by the Lineage Warehouse Services governance server.  
-
 * **[asset-manager](asset-manager)** - manage exchange of metadata with third party metadata catalogs and
 asset managers.