The enrich
processor can enrich documents with data from another index.
See enrich data section for more information about how to set this up.
Table 16. Enrich Options
Name | Required | Default | Description |
---|---|---|---|
|
yes |
- |
The name of the enrich policy to use. |
|
yes |
- |
The field in the input document that matches the policies match_field used to retrieve the enrichment data. Supports template snippets. |
|
yes |
- |
Field added to incoming documents to contain enrich data. This field contains both the |
|
no |
false |
If |
|
no |
true |
If processor will update fields with pre-existing non-null-valued field. When set to |
|
no |
1 |
The maximum number of matched documents to include under the configured target field. The |
|
no |
|
A spatial relation operator used to match the geoshape of incoming documents to documents in the enrich index. This option is only used for |
|
no |
- |
Description of the processor. Useful for describing the purpose of the processor or its configuration. |
|
no |
- |
Conditionally execute the processor. See Conditionally run a processor. |
|
no |
|
Ignore failures for the processor. See Handling pipeline failures. |
|
no |
- |
Handle failures for the processor. See Handling pipeline failures. |
|
no |
- |
Identifier for the processor. Useful for debugging and metrics. |