-
Notifications
You must be signed in to change notification settings - Fork 18
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
Implement the delete-history Command #1382
Comments
alexanderkiel
added a commit
that referenced
this issue
Sep 16, 2024
We need that functions in #1382 for the Jepsen tests.
github-merge-queue bot
pushed a commit
that referenced
this issue
Sep 16, 2024
We need that functions in #1382 for the Jepsen tests.
alexanderkiel
added a commit
that referenced
this issue
Sep 16, 2024
Before some reducible collections like from the iterators namespace and such created by the with-open-coll macro did not implement Counted. So they could not directly counted and instead had to be converted into a vector first. Needed by #1382
github-merge-queue bot
pushed a commit
that referenced
this issue
Sep 16, 2024
Before some reducible collections like from the iterators namespace and such created by the with-open-coll macro did not implement Counted. So they could not directly counted and instead had to be converted into a vector first. Needed by #1382
alexanderkiel
added a commit
that referenced
this issue
Sep 16, 2024
alexanderkiel
added a commit
that referenced
this issue
Sep 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We only like to delete the whole history (except for the current version). So we will implement:
Current draft FHIR spec: https://build.fhir.org/http.html#delete-history
Docs: https://github.com/samply/blaze/blob/main/docs/api.md#delete-history
We have to do:
delete-history
transaction commandt
of the new transaction and the identical value except fornum-changes
set to 1d/resource-handle
to determine the current value (hash, num-changes and op)blaze.db.impl.index.rts-as-of
TypeAsOf
andSystemAsOf
indices with thet
of the new transaction appended to the valuet
value is calledpurged-at
d/instance-history
to get all resource handles but drop the first onepurged-at
value means that the particular history entry was purged at this point in timenum-changes
ofTypeStats
andSystemStats
with the amount the deleted history entriesnum-changes
of the resource handle found minus 1d/instance-history
will just stop outputting resource handles ifnum-changes
is 1d/type-history
andd/system-history
will not output a resource handle if it'spurged-at
value is less or equal thet
of the current database statedelete-history
which will be called on DELETE on the history endpointblaze.rest-api.routes
This issue is part of the Epic: #399
The text was updated successfully, but these errors were encountered: