mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-06-28 17:34:17 -04:00
8067f01d48
Currently Elasticsearch always returns a shard failure once a runtime error arises from using a runtime field, the exception being script-less runtime fields. This also means that execution of the query for that shard stops, which is okay for development and exploration. In a production scenario, however, it is often desirable to ignore runtime errors and continue with the query execution. This change adds a new a new on_script_error parameter to runtime field definitions similar to the already existing parameter for index-time scripted fields. When `on_script_error` is set to `continue`, errors from script execution are effectively ignored. This means affected documents don't show up in query results, but also don't prevent other matches from the same shard. Runtime fields accessed through the fields API don't return values on errors, aggregations will ignore documents that throw errors. Note that this change affects scripted runtime fields only, while leaving default behaviour untouched. Also, ignored errors are not reported back to users for now. Relates to #72143 |
||
|---|---|---|
| .. | ||
| dynamic | ||
| fields | ||
| params | ||
| types | ||
| dynamic-mapping.asciidoc | ||
| explicit-mapping.asciidoc | ||
| fields.asciidoc | ||
| mapping-settings-limit.asciidoc | ||
| params.asciidoc | ||
| removal_of_types.asciidoc | ||
| runtime.asciidoc | ||
| types.asciidoc | ||