Add types for context events and lineage relationships #7934
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
These are the open metadata type definitions for:
First class support for events and actions. There will ultimately be a new framework, framework service and governance engine to support these types. The type definitions are going in to support this next stage of development.
Describing the ultimate source and destination of an element's lineage graph. This is to allow the Egeria UI to use the main metadata repository to retrieve ultimate source and destination lineage and an optional alternative to using the open lineage server.
Related Issue(s)
None
Testing
Unit test of types
Release Notes & Documentation
Updates to the documentation in place
Additional notes
None