Batched deletion of rendered content (#1959) #1969
Open
Conversation
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
|
@karimarie67 to allow sufficient testing on stage, this PR should get merged somewhat after a merge-to-master rather than immediately before, then it can be live on staging, multiple days. |
daveoconnor
changed the title
|
Selected Delete All Records. Got the message at the top of the page. 
I only had 114 records. Nothing appeared to be happening. I had to refresh the page to see results. If that is acceptable this is ready to go after review from @gregjkal |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
This is related to ticket #1959.
Adds batched deletion of rendered content through the admin UI. Deletes 10,000 rows at a time to reduce locking. Will continue until all rows are deleted, including recently added ones so we may see some re-added ones but CDN caching should mitigate that to some extent.
Testing:
in the admin UI under Rendered Content, click on "Delete All Rendered Content" and periodically check to confirm that the number goes down until none remain.