Add external source to create with template #8295
Merged
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
The OpenMetadataAccess API for the integration context was not passing the external source identifiers on createMetadataelementWithTemplate. This meant all elements created with a template ended up in the local cohort metadata collection. Problem fixed
Related Issue(s)
Also updated the file connectors to ignore
file://at the front of a file name when opening the file.Testing
Manual testing of cataloguing a unity catalog server and running a survey on one of the volumes
Release Notes & Documentation
None
Additional notes
There is also a change to the merge workflow to move the publish to maven central to the end of the workflow. This is because it fails from time to time and, when it ran first, this failure also stopped the publish of the containers to docker hub and quay.io. Reversing the order means that a problem with maven central only affects this part of the process