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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable pruning in the sandbox-classic when the append-only schema is used [DPP-567] #10708
Enable pruning in the sandbox-classic when the append-only schema is used [DPP-567] #10708
Changes from 2 commits
2158fee
1fa4ad8
77c5920
84f4c22
8c494e9
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is not enabling pruning, just pretending to prune, no?
how is the conformance tests pass then?
am I missing something? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I understand correctly the
ApiParticipantPruningService
performs pruning in two steps:For the
sandbox-classic
they are the same thing, so returningParticipantPruned
for the step 1. enables the step two.@mziolekda can you confirm that this is correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yupp, makes sense, a comment would be nice to clarify this behavior in the write service
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pruneAllDivulgedContracts
is not meant to be supported forsandbox-classic
because the backfiling lookup queries can start failing if used. Please returnUNIMPLEMENTED
if that flag is set. And please add a mention to the restriction in this method's doc/comments (e.g.Pruning of all divulged contracts is not supported on sandbox-classic
)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why can't we enable pruning for in-memory ledger?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe you can document it in the PR header why this one is left out
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is a corer case that we should not spend any time debating at this point. It would have to go through another story if we wanted that support.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fine by me. Just observed that there is no mention in the ticket or the PR regarding it.