From 239fc73f293483cb868fcb1bb90e9b2a18aec97d Mon Sep 17 00:00:00 2001 From: gui machiavelli Date: Thu, 4 Jan 2024 18:36:36 +0100 Subject: [PATCH] remove soft deletion from storage article --- learn/inner_workings/storage.mdx | 6 ------ 1 file changed, 6 deletions(-) diff --git a/learn/inner_workings/storage.mdx b/learn/inner_workings/storage.mdx index 17cd25624b..7ccc0fc8b5 100644 --- a/learn/inner_workings/storage.mdx +++ b/learn/inner_workings/storage.mdx @@ -71,9 +71,3 @@ These metrics are highly dependent on the machine that is running Meilisearch. R It is important to note that **there is no reliable way to predict the final size of a database**. This is true for just about any search engine on the market—we're just the only ones saying it out loud. Database size is affected by a large number of criteria, including settings, relevancy rules, use of facets, the number of different languages present, and more. - -## Soft deletion - -Meilisearch renders deleted documents inaccessible to all users but does not immediately remove them from the database. This is a common optimization technique called soft deletion. Soft deleted documents are permanently deleted during a later update, depending on your index size and the available disk space. It might be important to check how soft deletion interacts with data retention legislation relevant to your application. - -Soft deletion also affects document updates: when you update a document, Meilisearch removes the current record and creates a new document with updated data.