IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Rename processor
editRename processor
editRenames an existing field. If the field doesn’t exist or the new name is already used, an exception will be thrown.
Table 30. Rename Options
Name | Required | Default | Description |
---|---|---|---|
|
yes |
- |
The field to be renamed. Supports template snippets. |
|
yes |
- |
The new name of the field. Supports template snippets. |
|
no |
|
If |
|
no |
- |
Conditionally execute this processor. |
|
no |
- |
Handle failures for this processor. See Handling Failures in Pipelines. |
|
no |
|
Ignore failures for this processor. See Handling Failures in Pipelines. |
|
no |
- |
An identifier for this processor. Useful for debugging and metrics. |
{ "rename": { "field": "provider", "target_field": "cloud.provider" } }