From c0f85b6ff7d7192a516d6f770e3da5f263865a99 Mon Sep 17 00:00:00 2001 From: timvisee Date: Wed, 8 Apr 2026 17:01:48 +0200 Subject: [PATCH] Apply review suggestion Co-Authored-By: Abdon Pijpelink --- .../content/documentation/manage-data/indexing.md | 9 ++++----- qdrant-landing/static/llms-full.txt | 9 ++++----- 2 files changed, 8 insertions(+), 10 deletions(-) diff --git a/qdrant-landing/content/documentation/manage-data/indexing.md b/qdrant-landing/content/documentation/manage-data/indexing.md index f2a84eba2..40ff551fb 100644 --- a/qdrant-landing/content/documentation/manage-data/indexing.md +++ b/qdrant-landing/content/documentation/manage-data/indexing.md @@ -72,11 +72,10 @@ filters to `true`: | `false` | `true` | Parameterized integer index | | `false` | `false` | No integer index | -The parameterized index may help to tune and reduce memory usage in collections -with millions of points. We encourage you to try it out if mutual exclusively -using range or lookup payload filter types. If you don't see an improvement or -if you're not sure what kind of payload filters you're using, you can always go -back the regular `integer` index. +Setting `lookup` or `range` to `false` may help to tune and reduce memory usage +in large collections. We encourage you to try out if setting either to `false` +improves memory usage. If you don't see an improvement or if you're not sure +what kind of payload filters you're using, use the regular `integer` index. Note: If you set `"range": false` and still use a range filter, it may lead to significant performance issues. The same is true for the lookup parameter and diff --git a/qdrant-landing/static/llms-full.txt b/qdrant-landing/static/llms-full.txt index 44b2cb899..21ef9dfcb 100644 --- a/qdrant-landing/static/llms-full.txt +++ b/qdrant-landing/static/llms-full.txt @@ -28171,11 +28171,10 @@ filters to `true`: | `false` | `true` | Parameterized integer index | | `false` | `false` | No integer index | -The parameterized index may help to tune and reduce memory usage in collections -with millions of points. We encourage you to try it out if mutual exclusively -using range or lookup payload filter types. If you don't see an improvement or -if you're not sure what kind of payload filters you're using, you can always go -back the regular `integer` index. +Setting `lookup` or `range` to `false` may help to tune and reduce memory usage +in large collections. We encourage you to try out if setting either to `false` +improves memory usage. If you don't see an improvement or if you're not sure +what kind of payload filters you're using, use the regular `integer` index. Note: If you set `"range": false` and still use a range filter, it may lead to significant performance issues. The same is true for the lookup parameter and