Remove processor
Removes existing fields. If one field doesn’t exist, an exception will be thrown.
Table 33. Remove Options
| Name | Required | Default | Description |
|---|---|---|---|
| yes | - | Fields to be removed. Supports template snippets. |
| no |
| If |
| 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. |
Here is an example to remove a single field:
{
"remove": {
"field": "user_agent"
}
} To remove multiple fields, you can use the following query:
{
"remove": {
"field": ["user_agent", "url"]
}
}
© 2023-2025 Elasticsearch
As of September 2024, Elasticsearch is available under a choice of three licenses: the Server Side Public License (SSPL), the Elastic License, or the AGPLv3 (OSI approved).
Elasticsearch and the Elasticsearch logo are trademarks of Elasticsearch B.V., registered in the U.S. and in other countries.
https://www.elastic.co/guide/en/elasticsearch/reference/7.17/remove-processor.html