8218170711
Until today we could not search on the `met` field in the condition result. The reason for that is that this field was index as part of the condition result type only, and we disable the indexing for all condition results (to avoid mapping conflicts). This commit pulls the `met` condition one level higher and enables its mapping. For now (beta1) we can live with the duplication of the condition result source (were the `met` is not placed in both the condition result type and on the condition result itself). Later we should remove the duplication though. An example of a "compare" condition result now looks like: ``` "condition": { "met": true, "compare": { "met": true, "resolved_value": 1 } } ``` Original commit: elastic/x-pack-elasticsearch@74a3372c25 |
||
---|---|---|
dev-tools | ||
rest-api-spec | ||
src | ||
LICENSE.txt | ||
README.asciidoc | ||
all-signatures.txt | ||
core-signatures.txt | ||
pom.xml | ||
test-signatures.txt | ||
tests.policy |
README.asciidoc
= Elasticsearch Watcher Plugin This plugins adds conditioned scheduled tasks features to elasticsearch - such a task is called a `Watch`. You can build the plugin with `mvn package`. The documentation is put in the `docs/` directory.