d899c4b522
Until today it was required to provide a trigger event as part of the execute API. There are two issues with it: 1. It's not user friendly (you'd expect that the execute API would just work with just pointing to the watch) 2. The API could expose inconsistencies where on one hand it points to a watch (with a well defined trigger) on the other it enabled the user to provide completely different trigger (of a different type) This change enable supporting default triggers by enabling the trigger engine to create a simulated trigger event. This enables the execute API to look up the trigger type of the pointed watch, and ask the trigger service to simulate an event for it. It is still possible to override the trigger event data by providing it via the `trigger_data` parameter in the API. This simplifies the execute API and prepares it for future trigger types as well. - This commit add missing integration tests for the execute API - Also, removed unused `setIgnoreThrottling` from the execute request/builder. Original commit: elastic/x-pack-elasticsearch@b494ae62e6 |
||
|---|---|---|
| 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.