krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-09-30 00:18:32 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #2263 from qdrant/correct-param-index-note

Browse Source 
Correct parameterized index note
This commit is contained in:
Tim Visée
2026-05-15 17:46:49 +02:00
committed by GitHub
parent 1a0f06231c c0f85b6ff7
commit db67ab203f
2 changed files with 14 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/manage-data/indexing.md
+7 -5
View File
@@ -74,12 +74,14 @@ filters to `true`:
| `false` | `true` | Parameterized integer index |
| `false` | `false` | No integer index |
The parameterized index can enhance performance in collections with millions
of points. We encourage you to try it out. If it does not enhance performance
in your use case, you can always restore 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 `"lookup": true` with a range filter, that may lead to
significant performance issues.
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
its respective filters.
For example, the following code sets up a parameterized integer index which
supports only range filters:
qdrant-landing/static/llms-full.txt
+7 -5
View File
@@ -28171,12 +28171,14 @@ filters to `true`:
| `false` | `true` | Parameterized integer index |
| `false` | `false` | No integer index |
The parameterized index can enhance performance in collections with millions
of points. We encourage you to try it out. If it does not enhance performance
in your use case, you can always restore 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 `"lookup": true` with a range filter, that may lead to
significant performance issues.
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
its respective filters.
For example, the following code sets up a parameterized integer index which
supports only range filters: