mirror of
https://github.com/qdrant/landing_page.git
synced 2026-09-28 07:28:30 +02:00
Fixing links again (#697)
* 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:
@@ -50,7 +50,7 @@ For example, you will get an empty output if you apply the [range condition](../
|
||||
|
||||
However, arrays (multiple values of the same type) are treated a little bit different. When we apply a filter to an array, it will succeed if at least one of the values inside the array meets the condition.
|
||||
|
||||
The filtering process is discussed in detail in the section [Filtering](../filtering).
|
||||
The filtering process is discussed in detail in the section [Filtering](../filtering/).
|
||||
|
||||
Let's look at the data types that Qdrant supports for searching:
|
||||
|
||||
@@ -959,7 +959,7 @@ await client.DeletePayloadAsync(
|
||||
|
||||
To search more efficiently with filters, Qdrant allows you to create indexes for payload fields by specifying the name and type of field it is intended to be.
|
||||
|
||||
The indexed fields also affect the vector index. See [Indexing](../indexing) for details.
|
||||
The indexed fields also affect the vector index. See [Indexing](../indexing/) for details.
|
||||
|
||||
In practice, we recommend creating an index on those fields that could potentially constrain the results the most.
|
||||
For example, using an index for the object ID will be much more efficient, being unique for each record, than an index by its color, which has only a few possible values.
|
||||
|
||||
Reference in New Issue
Block a user