From c1052d704cf80d1624bb159dec1f35b423ca69aa Mon Sep 17 00:00:00 2001 From: Alain Pham Date: Thu, 4 May 2023 17:26:31 +0200 Subject: [PATCH] Update retention doc tsdb support of compactor (#9397) compactor now also supports tsdb in addition to boltdb-schipper **What this PR does / why we need it**: **Which issue(s) this PR fixes**: Fixes # **Special notes for your reviewer**: **Checklist** - [ ] Reviewed the [`CONTRIBUTING.md`](https://github.com/grafana/loki/blob/main/CONTRIBUTING.md) guide (**required**) - [ ] Documentation added - [ ] Tests updated - [ ] `CHANGELOG.md` updated - [ ] Changes that require user attention or interaction to upgrade are documented in `docs/sources/upgrading/_index.md` --- docs/sources/operations/storage/retention.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/operations/storage/retention.md b/docs/sources/operations/storage/retention.md index 93c112652f504..7c3dcf1a4d978 100644 --- a/docs/sources/operations/storage/retention.md +++ b/docs/sources/operations/storage/retention.md @@ -8,7 +8,7 @@ Retention in Grafana Loki is achieved either through the [Table Manager](#table- By default, when `table_manager.retention_deletes_enabled` or `compactor.retention_enabled` flags are not set, then logs sent to Loki live forever. -Retention through the [Table Manager]({{}}) is achieved by relying on the object store TTL feature, and will work for both [boltdb-shipper]({{}}) store and chunk/index store. However retention through the [Compactor]({{}}) is supported only with the [boltdb-shipper]({{}}) store. +Retention through the [Table Manager]({{}}) is achieved by relying on the object store TTL feature, and will work for both [boltdb-shipper]({{}}) store and chunk/index store. However retention through the [Compactor]({{}}) is supported only with the [boltdb-shipper]({{}}) and tsdb store. The Compactor retention will become the default and have long term support. It supports more granular retention policies on per tenant and per stream use cases.