Make it possible to force archiving for custom date ranges #14856
Conversation
This file contains 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
|
👏 yes please |
tsteur
reviewed
Sep 4, 2019
tsteur
requested changes
Sep 4, 2019
sgiehl
force-pushed
the
customperiodarchiving
branch
from
37f6260
to
e8aa013
Compare
sgiehl
force-pushed
the
customperiodarchiving
branch
from
e8aa013
to
e6dcd9f
Compare
|
@tsteur updated |
mattab
added
the
Enhancement
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In some cases it might be very useful to be able to define custom date ranges to be archived by
core:archive. E.g. if someone always wants to get the last 10 days stats via api, there is currently no way to get that pre-archived.The new config option would make it possible to define any range that is valid to be preprocessed