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

Fixing links again (#697)

Browse Source 
* use relative links instead of absolute

* add trailing slashes to avoid 301 redirect

* add trailing slashes to avoid 301 redirect

* make link checker unhappy with local redirects

* test if ci fails (should fail)

* rollback: test if ci fails (should fail)
This commit is contained in:
Andrey Vasnetsov
2024-03-07 20:31:05 +01:00
committed by GitHub
parent 2285373bc8
commit cae8456ce1
72 changed files with 142 additions and 140 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/concepts/search.md
+3 -3
View File
@@ -46,10 +46,10 @@ This process is called query planning.
The strategy selection process relies heavily on heuristics and can vary from release to release.
However, the general principles are:
* planning is performed for each segment independently (see [storage](../storage) for more information about segments)
* planning is performed for each segment independently (see [storage](../storage/) for more information about segments)
* prefer a full scan if the amount of points is below a threshold
* estimate the cardinality of a filtered result before selecting a strategy
* retrieve points using payload index (see [indexing](../indexing)) if cardinality is below threshold
* retrieve points using payload index (see [indexing](../indexing/)) if cardinality is below threshold
* use filterable vector index if the cardinality is above a threshold
You can adjust the threshold using a [configuration file](https://github.com/qdrant/qdrant/blob/master/config/config.yaml), as well as independently for each collection.
@@ -211,7 +211,7 @@ Currently, it could be:
* `indexed_only` - With this option you can disable the search in those segments where vector index is not built yet. This may be useful if you want to minimize the impact to the search performance whilst the collection is also being updated. Using this option may lead to a partial result if the collection is not fully indexed yet, consider using it only if eventual consistency is acceptable for your use case.
Since the `filter` parameter is specified, the search is performed only among those points that satisfy the filter condition.
See details of possible filters and their work in the [filtering](../filtering) section.
See details of possible filters and their work in the [filtering](../filtering/) section.
Example result of this API would be