Extract Field Action
Provided by: "Apache Software Foundation"
Support Level for this Kamelet is: "Stable"
Extract a field from the message body.
The extract field action expects an application/json content type.
The field parameter allows you to specify which field of the json the user wants to extract. By default the message body will be overriden with the extracted field.
The optional parameter headerOutput allows the user to specify wheter the extracted field should be stored in a message header named 'CamelKameletsExtractFieldName', leaving the message body untouched.
The optional parameter headerOutputName allows the user to specify a custom header name instead of the default 'CamelKameletsExtractFieldName'. This parameter must be used in conjunction with headerOutput. If no headerOutputName parameter will be provided, the default 'CamelKameletsExtractFieldName' will be used.
The optional parameter strictHeaderCheck allows to user to enable a strict header name check. If enabled the action will check if the header output name (custom or default) has been used already in the exchange. If so, the extracted field will be stored in the message body, if not, the extracted field will be stored in the selected header (custom or default).
The headerOutput/headerOutputName/strictHeaderCheck parameters are particulary useful in case you would like to reuse an extracted field as parameter for another header, for example.
Configuration Options
The following table summarizes the configuration options available for the extract-field-action
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
Field |
Required The name of the field to extract. |
string |
|||
Header Output |
If enable the action will store the extracted field in an header named CamelKameletsExtractFieldName. |
boolean |
false |
||
Header Output Name |
A custom name for the header containing the extracted field. |
string |
none |
||
Strict Header Check |
If enabled the action will check if the header output name (custom or default) has been used already in the exchange. If so, the extracted field will be stored in the message body, if not, the extracted field will be stored in the selected header (custom or default). |
boolean |
false |
Dependencies
At runtime, the extract-field-action
Kamelet relies upon the presence of the following dependencies:
-
github:apache.camel-kamelets:camel-kamelets-utils:0.9.4-SNAPSHOT
-
camel:kamelet
-
camel:core
-
camel:jackson
Usage
This section describes how you can use the extract-field-action
.
Knative action
You can use the extract-field-action
Kamelet as an intermediate step in a Knative binding.
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
name: extract-field-action-binding
spec:
source:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1alpha1
name: timer-source
properties:
message: Hello
steps:
- ref:
kind: Kamelet
apiVersion: camel.apache.org/v1alpha1
name: extract-field-action
properties:
field: The Field
sink:
ref:
kind: Channel
apiVersion: messaging.knative.dev/v1
name: mychannel
Prerequisite
You have Camel K installed on the cluster.
Kafka action
You can use the extract-field-action
Kamelet as an intermediate step in a Kafka binding.
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
name: extract-field-action-binding
spec:
source:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1alpha1
name: timer-source
properties:
message: Hello
steps:
- ref:
kind: Kamelet
apiVersion: camel.apache.org/v1alpha1
name: extract-field-action
properties:
field: The Field
sink:
ref:
kind: KafkaTopic
apiVersion: kafka.strimzi.io/v1beta1
name: my-topic
Prerequisites
-
You’ve installed Strimzi.
-
You’ve created a topic named
my-topic
in the current namespace. -
You have Camel K installed on the cluster.