2023-08-29 16:07:34 -04:00
---
layout: default
title: Remove
2023-10-17 17:22:28 -04:00
parent: Ingest processors
2023-08-29 16:07:34 -04:00
nav_order: 230
2023-10-17 17:22:28 -04:00
redirect_from:
- /api-reference/ingest-apis/processors/remove/
2023-08-29 16:07:34 -04:00
---
2023-12-05 14:49:46 -05:00
# Remove processor
2023-08-29 16:07:34 -04:00
2023-10-23 10:53:52 -04:00
The `remove` processor is used to remove a field from a document.
2023-12-12 15:16:16 -05:00
## Syntax
2023-10-23 10:53:52 -04:00
The following is the syntax for the `remove` processor:
2023-08-29 16:07:34 -04:00
```json
{
"remove": {
"field": "field_name"
}
}
```
{% include copy-curl.html %}
2023-12-12 15:16:16 -05:00
## Configuration parameters
2023-08-29 16:07:34 -04:00
The following table lists the required and optional parameters for the `remove` processor.
2023-12-12 15:16:16 -05:00
| Parameter | Required/Optional | Description |
2023-08-29 16:07:34 -04:00
|---|---|---|
2024-01-26 15:47:22 -05:00
`field` | Optional | The field name containing the data to be removed. Supports [template snippets ]({{site.url}}{{site.baseurl}}/ingest-pipelines/create-ingest/#template-snippets ). The metadata fields `_index` , `_version` , `_version_type` , and `_id` cannot be removed. If `version` is specified, `_id` cannot be removed from the ingested document. |
`exclude_field` | Optional | The field name to be retained. All other fields, except metadata fields, will be removed. The `exclude_field` and `field` options are mutually exclusive. Supports [template snippets ]({{site.url}}{{site.baseurl}}/ingest-pipelines/create-ingest/#template-snippets ). |
2023-08-29 16:07:34 -04:00
`description` | Optional | A brief description of the processor. |
2023-12-12 15:16:16 -05:00
`if` | Optional | A condition for running the processor. |
`ignore_failure` | Optional | Specifies whether the processor continues execution even if it encounters errors. If set to `true` , failures are ignored. Default is `false` . |
2023-08-29 16:07:34 -04:00
`on_failure` | Optional | A list of processors to run if the processor fails. |
2023-12-12 15:16:16 -05:00
`tag` | Optional | An identifier tag for the processor. Useful for debugging in order to distinguish between processors of the same type. |
2023-08-29 16:07:34 -04:00
## Using the processor
Follow these steps to use the processor in a pipeline.
2023-12-12 15:16:16 -05:00
**Step 1: Create a pipeline**
2023-08-29 16:07:34 -04:00
The following query creates a pipeline, named `remove_ip` , that removes the `ip_address` field from a document:
```json
PUT /_ingest/pipeline/remove_ip
{
"description": "Pipeline that excludes the ip_address field.",
"processors": [
{
"remove": {
"field": "ip_address"
}
}
]
}
```
{% include copy-curl.html %}
2023-12-12 15:16:16 -05:00
**Step 2 (Optional): Test the pipeline**
2023-08-29 16:07:34 -04:00
It is recommended that you test your pipeline before you ingest documents.
{: .tip}
To test the pipeline, run the following query:
```json
POST _ingest/pipeline/remove_ip/_simulate
{
"docs": [
{
"_index": "testindex1",
"_id": "1",
"_source":{
"ip_address": "203.0.113.1",
"name": "John Doe"
}
}
]
}
```
{% include copy-curl.html %}
2023-12-12 15:16:16 -05:00
**Response**
2023-08-29 16:07:34 -04:00
The following example response confirms that the pipeline is working as expected:
```json
{
"docs": [
{
"doc": {
"_index": "testindex1",
"_id": "1",
"_source": {
"name": "John Doe"
},
"_ingest": {
"timestamp": "2023-08-24T18:02:13.218986756Z"
}
}
}
]
}
```
2023-12-12 15:16:16 -05:00
**Step 3: Ingest a document**
2023-08-29 16:07:34 -04:00
The following query ingests a document into an index named `testindex1` :
```json
2024-01-31 13:11:30 -05:00
PUT testindex1/_doc/1?pipeline=remove_ip
2023-08-29 16:07:34 -04:00
{
"ip_address": "203.0.113.1",
"name": "John Doe"
}
```
{% include copy-curl.html %}
2023-12-12 15:16:16 -05:00
**Step 4 (Optional): Retrieve the document**
2023-08-29 16:07:34 -04:00
To retrieve the document, run the following query:
```json
GET testindex1/_doc/1
```
{% include copy-curl.html %}