Repository navigation
docs(issues): ISSUE-117 -- cascade delete on the soft-delete path fails partway without forLineage - #416
Merged
Conversation
…ls partway without forLineage Found cleaning up after the Automation family's live subscription test and reproduced the same day: a fresh asset cascade-deletes (purges) fine, but an asset Egeria soft-deletes (here, one used as a subscription destination) fails with OMAG-REPOSITORY-HANDLER-400-010 after already Memento'ing an anchored Endpoint. Workaround: forLineage=true on the delete. Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>
ISSUE-115 and ISSUE-116 were taken on main by odpi#415's My Profile entries while this PR was open. Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>
dwolfson
changed the title
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.
Records a new Egeria Server issue found while cleaning up after the Automation family's live subscription test (#414). I meant to include it in #414, but that PR merged first.
What happens: cascade-deleting an asset that Egeria soft-deletes (Memento), rather than purges, fails with
OMAG-REPOSITORY-HANDLER-400-010. That happened here for an asset used as a subscription destination. The call has already Memento'd an anchored Endpoint when it fails, so the asset is left live with its Endpoint soft-deleted.Reproduced the same day: a fresh asset cascade-deletes (purges) fine with the identical call. The partial-delete timing is confirmed from the Memento classification's own timestamps.
Workaround: send
forLineage: trueon the delete. Dr.Egeria editing commands already do this by default (6.1.25).Documentation only; no code changes.
🤖 Generated with Claude Code