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

additional information for the lookup collection

Browse Source
This commit is contained in:
Sabrina
2025-01-22 23:55:19 -03:00
parent cfcb242b6a
commit 58d7cf6c61
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/concepts/search.md
+5 -1
View File
@@ -1644,6 +1644,8 @@ One way of optimizing storage when using groups is to store the information shar
![Group id matches point id](/docs/lookup_id_linking.png)
<aside role="status">Store only document-level metadata (e.g., titles, abstracts) in the lookup collection, not chunks or duplicated data.</aside>
This has the extra benefit of having a single point to update when the information shared by the points in a group changes.
For example, if you have a collection of documents, you may want to chunk them and store the points for the chunks in a separate collection, making sure that you store the point id from the document it belongs in the payload of the chunk point.
@@ -1851,7 +1853,9 @@ The looked up result will show up under `lookup` in each group.
}
```
Since the lookup is done by matching directly with the point id, any group id that is not an existing (and valid) point id in the lookup collection will be ignored, and the `lookup` field will be empty.
Since the lookup is done by matching directly with the point id, the lookup collection must be pre-populated with points where the `id` matches the `group_by` value (e.g., document_id) from your primary collection.
Any group id that is not an existing (and valid) point id in the lookup collection will be ignored, and the `lookup` field will be empty.
## Random Sampling