Replace Field Action
Provided by: "Apache Software Foundation"
Support Level for this Kamelet is: "Stable"
Replace field with a different key in the message in transit.
Configuration Options
The following table summarizes the configuration options available for the replace-field-action Kamelet:
| Property | Name | Description | Type | Default | Example |
|---|---|---|---|---|---|
Renames | Required Comma separated list of field with new value to be renamed. Only top level fields are renamed; naming a field nested inside an object has no effect. | string | foo:bar,c1:c2 | ||
Disabled | Comma separated list of top level fields to be disabled. | string | none | ||
Enabled | Comma separated list of top level fields to be enabled. | string | all |
Dependencies
At runtime, the replace-field-action Kamelet relies upon the presence of the following dependencies:
-
camel:core
-
camel:jackson
-
camel:kamelet
-
camel:kafka
Camel JBang usage
Prerequisites
-
You’ve installed JBang.
-
You have executed the following command:
jbang app install camel@apache/camelSupposing you have a file named route.yaml with this content:
- route:
from:
uri: "kamelet:timer-source"
parameters:
period: 10000
message: 'test'
steps:
- to:
uri: "kamelet:replace-field-action"
parameters:
.
.
.
- to:
uri: "kamelet:log-sink"You can now run it directly through the following command
camel run route.yamlReplace Field Action Kamelet Description
Scope
Only top level fields are considered. Fields nested inside an object are passed through untouched, so a rename that names a nested field has no effect.
The enabled and disabled properties filter on the same top level keys.
For example, with a body of {"message":{"Hola":"mundo"}}, renaming message works while renaming Hola does nothing.