You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presently when using the deleteSummarizedOps.ts when the aggregated data regarding all the unique documentIds is passed, the process iterates through each of those and then adds soft delete markers to deltas (where applicable) and does hard delete of deltas (where applicable). And this is done in a sequential manner for each of the documents which are passed in.
Now the issue is whenever there is an error occurring for any of the documents, all the documents there after are not handled and the loop breaks in between
To Reproduce
Steps to reproduce the behavior:
Intentionally delete the content block from one of the DOCUMENTS#tenant#documentId collection item
Enable the softDeletionEnabled flag
Restart scriptorium
See error as follows
Expected behavior
Ideally the error should be logged for the document for which the failure happens and all the subsequent documents deletion should take place
arafat-java
changed the title
Handle checkpoint error and proceed with remaining ops deletion batch
Error in fetching checkpoint for any document causes rest of the batch to fail in deleteSummarizedOps
Apr 12, 2024
arafat-java
changed the title
Error in fetching checkpoint for any document causes rest of the batch to fail in deleteSummarizedOps
Error fetching checkpoint for any document causes rest of the batch to fail in deleteSummarizedOps
Apr 12, 2024
Describe the bug
Presently when using the deleteSummarizedOps.ts when the aggregated data regarding all the unique documentIds is passed, the process iterates through each of those and then adds soft delete markers to deltas (where applicable) and does hard delete of deltas (where applicable). And this is done in a sequential manner for each of the documents which are passed in.
Now the issue is whenever there is an error occurring for any of the documents, all the documents there after are not handled and the loop breaks in between
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Ideally the error should be logged for the document for which the failure happens and all the subsequent documents deletion should take place
Logs
The text was updated successfully, but these errors were encountered: