Skip to content
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

Support aging out data based on a query #929

Merged
merged 1 commit into from
Jun 18, 2020
Merged

Conversation

dominiklohmann
Copy link
Member

@dominiklohmann dominiklohmann commented Jun 17, 2020

Note: For now, this only supports aging out data from the archive, not from the index.

An aging cycle can be manually triggered by running:

vast send eraser run

The newly added options system.aging-frequency and system.aging-query can be used for configuring the eraser component.

@dominiklohmann dominiklohmann added the feature New functionality label Jun 17, 2020
@dominiklohmann dominiklohmann marked this pull request as ready for review June 17, 2020 10:02
@dominiklohmann dominiklohmann requested a review from a team June 17, 2020 10:02
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
Note: For now, this only supports aging out data from the archive, not from
the index.

An aging cycle can be manually triggered by running:

    vast send eraser run

The newly added options `system.aging-frequency` and
`system.aging-query` can be used for configuring the eraser component.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants