feat(ldes-client): adjust tombstone handling #217
Merged
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.
Overview
This PR includes some modifications in how we handle tombstone (deleted) resources in the lmb ldes-client.
Specifically this PR includes:
processPage.ts
to remove incoming tombstones resources completely from our database (all related triples)connected issues and PRs:
None
Setup
Ensure you have the
ldes-client
service set-up locallyHow to test/reproduce
Scenario 1: starting from an empty database
ldes-client
to your LMB environment of choiceldes-client
and let it run (to completion)Scenario 2: starting from a DEV/QA/PROD backup
Challenges/uncertainties
UNION
instead ofOPTIONAL
as it is more performantResultSetMaxRows
to fully executeChecks PR readiness