Merge pull request #2079 from qdrant/docs-filtrable-filterable

Standardize on 'filterable' instead of 'filtrable'
This commit is contained in:
Abdon Pijpelink
2026-01-15 16:25:42 +01:00
committed by GitHub
44 changed files with 42 additions and 42 deletions
@@ -88,7 +88,7 @@ Qdrant is an AI-native vector database and a semantic search engine. You can use
## Qdrant's most popular features:
||||
|:-|:-|:-|
|[Filtrable HNSW](/documentation/filtering/) </br> Single-stage payload filtering | [Recommendations & Context Search](/documentation/concepts/explore/#explore-the-data) </br> Exploratory advanced search| [Pure-Vector Hybrid Search](/documentation/hybrid-queries/)</br>Full text and semantic search in one|
|[Filterable HNSW](/documentation/filtering/) </br> Single-stage payload filtering | [Recommendations & Context Search](/documentation/concepts/explore/#explore-the-data) </br> Exploratory advanced search| [Pure-Vector Hybrid Search](/documentation/hybrid-queries/)</br>Full text and semantic search in one|
|[Multitenancy](/documentation/guides/multiple-partitions/) </br> Payload-based partitioning|[Custom Sharding](/documentation/guides/distributed_deployment/#sharding) </br> For data isolation and distribution|[Role Based Access Control](/documentation/guides/security/?q=jwt#granular-access-control-with-jwt)</br>Secure JWT-based access |
|[Quantization](/documentation/guides/quantization/) </br> Compress data for drastic speedups|[Multivector Support](/documentation/concepts/vectors/?q=multivect#multivectors) </br> For ColBERT late interaction |[Built-in IDF](/documentation/concepts/indexing/?q=inverse+docu#idf-modifier) </br> Advanced similarity calculation|
@@ -339,7 +339,7 @@ Where:
- `N` is the total number of documents in the collection.
- `n` is the number of documents containing non-zero values for the given vector element.
## Filtrable Index
## Filterable Index
Separately, a payload index and a vector index cannot solve the problem of search using the filter completely.
@@ -356,7 +356,7 @@ On the other hand, the HNSW graph starts to fall apart when using too strict fil
Qdrant solves this problem by extending the HNSW graph with additional edges based on the stored payload values.
Extra edges allow you to efficiently search for nearby vectors using the HNSW index and apply filters as you search in the graph.
You can find more information on this approach in our [article](/articles/filtrable-hnsw/).
You can find more information on this approach in our [article](/articles/filterable-hnsw/).
However, in some cases, these additional edges might not be enough.
These extra edges are added per each payload index separately, but not per each possible combination of them.
@@ -175,7 +175,7 @@ Accessing array elements by index is currently not supported.
*Available as of v1.16.0*
For filtered vector search, you are recommended to create a [payload index](/documentation/concepts/indexing/#payload-index) for the fields you want to filter by.
During the search, Qdrant will use a combined [filterable index](/documentation/concepts/indexing/#filtrable-index).
During the search, Qdrant will use a combined [filterable index](/documentation/concepts/indexing/#filterable-index).
However, when combining multiple strict payload filters, this mechanism might not provide sufficient accuracy.
In such cases, you can use the ACORN search algorithm.