Repository navigation
docs(issues): log ISSUE-128..134, verify 127/129/131 against Egeria source - #438
Merged
Merged
Conversation
…ource - ISSUE-128, 130: Egeria server bugs (Retention subtype typo; YAML secrets store caches users forever), logged by the Resource Explorer session. - ISSUE-129: get_related_metadata_elements and two linked-by-* siblings drop paging/lineage arguments. Contract checked against MetadataExpertResource.java: startingAtEnd is a current query parameter on related-elements only. - ISSUE-131: 13 (not 27) *_by_name wrappers drop the type filter; the 14 find_* grep hits are correct. - ISSUE-132: DeleteElementRequestBody sends cascadeDelete, Egeria reads cascadedDelete and ignores unknown fields. On hold for an Egeria fix. - ISSUE-133: governance_officer reads subComponents; Egeria 6.2 returns nestedSolutionComponents. - ISSUE-134: PYEGERIA_ENABLE_LOGGER_CATCH makes @dynamic_catch return None on any failure. - ISSUE-126/127: marked merged in odpi#429; 127 is only partly fixed (ISSUE-132). Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>
…s impact The governance_officer formatter ISSUE-133 named as the real bug has no callers, so no live output was affected. Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>
This file contains hidden or 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
1 participant
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.
Documentation only: updates to
PYEGERIA_ISSUES.md. No code changes.New entries
RetentionProperties.class. Waiting for the Egeria fix.MetadataExpert.get_related_metadata_elementsand the twolinked-by-*relationship queries accept paging, direction and lineage arguments but never send them. Verified againstMetadataExpertResource.java:startingAtEndis a current query parameter on therelated-elementsendpoints only, and the rest belong inResultsRequestBody.*_by_namewrappers passmetadata_element_type=to_async_get_name_request, which readsmetadata_element_type_name, so the type filter is dropped. The 14find_*matches for the same grep are correct.DeleteElementRequestBodysendscascadeDelete, but Egeria'sDeleteOptionsfield iscascadedDeleteand unknown fields are ignored, so no cascade delete through pyegeria has reached Egeria. On hold for an upcoming Egeria cascade-delete fix; it will be live-tested against that first.governance_officer.pyreadssubComponents, but Egeria 6.2 returnsnestedSolutionComponents.PYEGERIA_ENABLE_LOGGER_CATCHon,@dynamic_catchreturnsNoneon any failure, which looks the same as "nothing found".Updated entries
Server-side claims were checked against Egeria source at
af400039c2(2026-10-06), not only the.httpfiles. Nothing here was live-tested.🤖 Generated with Claude Code