add minimal documentation for expression filters (#11045)

* add minimal documentation for expression filters

* Update docs/querying/filters.md

Co-authored-by: Clint Wylie <cjwylie@gmail.com>

* Update docs/querying/filters.md

Co-authored-by: sthetland <steve.hetland@imply.io>

* Update docs/querying/filters.md

Co-authored-by: Alejandro Lujan <andanthor@gmail.com>

* Update docs/querying/filters.md

Co-authored-by: Alejandro Lujan <andanthor@gmail.com>

Co-authored-by: Clint Wylie <cjwylie@gmail.com>
Co-authored-by: sthetland <steve.hetland@imply.io>
Co-authored-by: Alejandro Lujan <andanthor@gmail.com>
This commit is contained in:
Cameron Teasdale 2021-04-07 19:58:28 -04:00 committed by GitHub
parent b51ede5b49
commit 786207995e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 15 additions and 0 deletions

View File

@ -531,3 +531,18 @@ The true filter is a filter which matches all values. It can be used to tempora
{ "type" : "true" }
```
### Expression Filter
The expression filter allows for the implementation of arbitrary conditions, leveraging the Druid expression system.
This filter allows for more flexibility, but it might be less performant than a combination of the other filters on this page due to the fact that not all filter optimizations are in place yet.
```json
{
"type" : "expression" ,
"expression" : "((product_type == 42) && (!is_deleted))"
}
```
See the [Druid expression system](../misc/math-expr.md) for more details.