Egeria, an LF AI & Data Foundation Graduate Project, has released version 2.8! Egeria is an open source project dedicated to making metadata open and automatically exchanged between tools and platforms, no matter which vendor they come from.
In version 2.8, Egeria adds a variety of improvements. Highlights include:
- New support for event and property filtering for the open metadata server security connector
- The repository services support 3 filtering points for managing events for the OMRS Cohort Topic, however, the filtering points are set up in the configuration document of the server. This configuration provides no control to allow filtering of events for specific instances. Version 2.8 extends the metadata server security connector so it can be called at these same filter points.
- The security server connector will have two new interfaces that it can implement: one for the cohort events and one for saving events to the local repository.
- The event interface will have two methods, one for sending and one for receiving. The parameters will include the cohort name and the event contents. It can return the event unchanged, return a modified event (e.g. with sensitive content removed) or return null to say that the event is filtered out.
- The event saving interface will receive the instance header and can return a boolean to indicate if the local repository should store it. If true is returned, the refresh event sequence is initiated. The repository connector then has the ultimate choice when the refreshed instance is returned from the home repository as to whether to store it or not.
- Changes to metadata types
- Updates to the location types in model 0025:
- Add the mapProjection property to the FixedLocation classification
- Change the address property to networkAddress in the CyberLocation classification
- Deprecated HostLocation in favor of the AssetLocation relationship
- Deprecate the RuntimeForProcess relationship since it is superfluous – use ServerAssetUse since Application is a SoftwareServerCapability.
- Replace the deployedImplementationType property with the businessCapabilityType in the BusinessCapability since it is a more descriptive name.
- Updates to the location types in model 0025:
- New performance workbench for the CTS (technical preview)
- The performance workbench intends to test the response time of all repository (metadata collection) methods for the technology under test. The volume of the test can be easily configured to also test scalability.
- New interface for retrieving the complete history of a single metadata instance
- Two new (optional) methods have been introduced to the metadata collection interface:
- getEntityDetailHistory
- getRelationshipHistory
- Both methods take the GUID of the instance for which to retrieve history, an optional range of times between which to retrieve the historical versions (or if both are null to retrieve all historical versions), and a set of paging parameters.
- If not implemented by a repository, these will simply throw FunctionNotSupported exceptions by default to indicate that they are not implemented.
- Two new (optional) methods have been introduced to the metadata collection interface:
- Splitting of CTS results into multiple smaller files
- Up to this release, the detailed results of a CTS run could only be retrieved by pulling a huge (100’s of MB) file across the REST interface for the CTS. Aside from not typically working with most REST clients (like Postman), this had the additional impact of a sudden huge hit on the JVM heap to serialize such a large JSON structure (immediately grabbing ~1GB of the heap). While this old interface still exists for backwards compatibility, the new default interface provided in this release allows users to pull down just an overall summary of the results separately from the full detailed results, and the detailed results are now broken down into separate files by profile and test case: each of which can therefore be retrieved individually.
- Bug fixes and other updates
- Additional Bug Fixes
- Dependency Updates
To learn more about the Egeria 2.8 release, check out the full release notes. Want to get involved with Egeria? Be sure to join the Egeria-Announce and Egeria-Technical-Discuss mailing lists to join the community and stay connected on the latest updates.
Congratulations to the Egeria team and we look forward to continued growth and success as part of the LF AI & Data Foundation! To learn about hosting an open source project with us, visit the LF AI & Data Foundation website.
Egeria Key Links
LF AI & Data Resources
-
- Learn about membership opportunities
- Explore the interactive landscape
- Check out our technical projects
- Join us at upcoming events
- Read the latest announcements on the blog
- Subscribe to the mailing lists
- Follow us on Twitter or LinkedIn
- Access other resources on LF AI & Data’s GitHub or Wiki
