Repository navigation
feat(asset-catalog): maxHops and skipRelationships on the lineage graph (Egeria 6.3) - #526
Merged
Merged
Conversation
…ph (Egeria 6.3) Egeria 6.3 (odpi/egeria#9420) cuts the asset lineage walk at maxHops (default 8, 0 = no limit) and marks each node with hopsFromStart and hopLimitReached; skipRelationships now works and RequestForActionTarget and AssignmentScope are no longer followed by default. - get_asset_lineage_graph_by_guid (async and sync) and get_asset_lineage_mermaid_graph take max_hops and skip_relationships, sent only when set, so a 6.2 platform sees the same body as before. - A per-call timeout reaches _async_make_request (kwargs were dropped). - Docstrings: relationship_types replaces the defaults and accepts supertypes; the 6.3 default list; max_mermaid_node_count defaults to 10. - New Asset-Lineage-Hops report spec and lineage_hop_summary(): one row per node with hopsFromStart/hopLimitReached, headed by "Graph cut at N hops · M elements continue past the limit". A pre-6.3 graph is reported as of unknown completeness, never as complete, and the Mermaid helper logs a warning when the graph was cut. - Micro-tests capture the request body and check the summary. Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>
dwolfson
added a commit
that referenced
this pull request
Nov 3, 2026
6.2.20 ships #526: max_hops / skip_relationships / timeout on the asset lineage graph methods for Egeria 6.3 (odpi/egeria#9420), and the Asset-Lineage-Hops report spec with lineage_hop_summary(). Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>
This was referenced Nov 4, 2026
chore: pyegeria>=6.2.20 everywhere; freshstart platform pin to Egeria 6.3
odpi/egeria-workspaces#751
Open
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
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.
Adopts odpi/egeria#9420 (Egeria 6.3, "Improve efficiency of the asset graph") in
AssetCatalog.Request:
_async_get_asset_lineage_graph_by_guid,get_asset_lineage_graph_by_guidandget_asset_lineage_mermaid_graphgainmax_hops(→maxHops; Egeria's default is 8,0= no limit) andskip_relationships(→skipRelationships, now honoured by the walk)._async_make_request; previously**kwargswas dropped, so amax_hops=0caller was stuck on the 30 s client default.relationship_typesreplaces the defaults and accepts supertypes (LineageRelationship,DataLineageRelationship).max_mermaid_node_countdefaults to 10.Output:
Asset-Lineage-Hopsreport spec andlineage_hop_summary()give one row per node withhopsFromStart/hopLimitReached, headed "Graph cut at N hops · M elements continue past the limit".Checks:
AssetLineageGraphRequestBody.maxHops,skipRelationshipsandincludeOnlyRelationshipson the options base, andAssetLineageGraphNode.hopsFromStart/hopLimitReached.as-lineage-graphreturnshopsFromStartthere.🤖 Generated with Claude Code