mirror of
https://github.com/qdrant/landing_page.git
synced 2026-10-01 08:58:31 +02:00
Add text_any filter condition docs for 1.16
This commit is contained in:
@@ -319,6 +319,14 @@ If there is no full-text index for the field, the condition will work as exact s
|
||||
|
||||
If the query has several words, then the condition will be satisfied only if all of them are present in the text.
|
||||
|
||||
### Text Any
|
||||
|
||||
*Available as of v1.16.0*
|
||||
|
||||
The `text_any` full-text match condition is similar to the `text` condition, but with a key difference: while `text` only matches text fields that contain *all* the query terms, `text_any` matches fields that contain *any* of the query terms. In other words, even if a text field contains just one of the query terms, it is considered a match.
|
||||
|
||||
{{< code-snippet path="/documentation/headless/snippets/filter-condition/full-text-match-any/" >}}
|
||||
|
||||
### Phrase Match
|
||||
|
||||
*Available as of v1.15.0*
|
||||
|
||||
+1
@@ -0,0 +1 @@
|
||||
This code snippet sets up a field condition to search for one or more query terms within a text field. In this case, a special `text_any` match is defined with the target text being "good cheap". The behavior may vary depending on the configuration of the full-text index for the field. If there is no full-text index configured for the field, the condition will work as an exact substring match.
|
||||
+8
@@ -0,0 +1,8 @@
|
||||
```json
|
||||
{
|
||||
"key": "description",
|
||||
"match": {
|
||||
"text_any": "good cheap"
|
||||
}
|
||||
}
|
||||
```
|
||||
+6
@@ -0,0 +1,6 @@
|
||||
```typescript
|
||||
{
|
||||
key: 'description',
|
||||
match: {text_any: 'good cheap'}
|
||||
}
|
||||
```
|
||||
Reference in New Issue
Block a user