Additional threshold for deleting task history row#1369
Merged
Conversation
Contributor
Author
|
This PR is into the |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Building off of the previous history purge update PR and I'll merge the two. This separates out settings for deleting task history bytes versus the entire task history row in the db. Rows to delete are checked/purged first, followed by rows to update bytes.
deleteTaskHistoryBytes...settings take on the previous default values of 365 days/10k tasks since that was the previous default behaviordeleteTaskHistory...settings default to 0 so the rows are not deleted by default