이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Kamelets reference for Red Hat build of Apache Camel for Quarkus
Kamelets reference for Red Hat build of Apache Camel for Quarkus
Abstract
Preface
Providing feedback on Red Hat build of Apache Camel documentation
To report an error or to improve our documentation, log in to your Red Hat Jira account and submit an issue. If you do not have a Red Hat Jira account, then you will be prompted to create an account.
Procedure
- Click the following link to create ticket
- Enter a brief description of the issue in the Summary.
- Provide a detailed description of the issue or enhancement in the Description. Include a URL to where the issue occurs in the documentation.
- Clicking Submit creates and routes the issue to the appropriate documentation team.
1. AWS DynamoDB Sink
Send data to AWS DynamoDB service. The sent data will insert/update/delete an item on the given AWS DynamoDB table.
Access Key/Secret Key are the basic method for authenticating to the AWS DynamoDB service. These parameters are optional, because the Kamelet also provides the following option 'useDefaultCredentialsProvider'.
When using a default Credentials Provider the AWS DynamoDB client will load the credentials through this provider and won’t use the static credential. This is the reason for not having access key and secret key as mandatory parameters for this Kamelet.
This Kamelet expects a JSON field as body. The mapping between the JSON fields and table attribute values is done by key, so if you have the input as follows:
{"username":"oscerd", "city":"Rome"}
The Kamelet will insert/update an item in the given AWS DynamoDB table and set the attributes 'username' and 'city' respectively. Please note that the JSON object must include the primary key values that define the item.
1.1. Configuration Options
The following table summarizes the configuration options available for the aws-ddb-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
region * | AWS Region | The AWS region to connect to |
|
| |
table * | Table | Name of the DynamoDB table to look at |
| ||
accessKey | Access Key | The access key obtained from AWS |
| ||
operation | Operation | The operation to perform (one of PutItem, UpdateItem, DeleteItem) | string |
|
|
overrideEndpoint | Endpoint Overwrite | Set the need for overiding the endpoint URI. This option needs to be used in combination with uriEndpointOverride setting. |
|
| |
secretKey | Secret Key | The secret key obtained from AWS |
| ||
uriEndpointOverride | Overwrite Endpoint URI | Set the overriding endpoint URI. This option needs to be used in combination with overrideEndpoint option. |
| ||
useDefaultCredentialsProvider | Default Credentials Provider | Set whether the DynamoDB client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. |
|
| |
useProfileCredentialsProvider | Profile Credentials Provider | Set whether the DynamoDB client should expect to load credentials through a profile credentials provider. |
|
| |
useSessionCredentials | Session Credentials | Set whether the DynamoDB client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in DynamoDB. |
|
| |
profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter will set the profile name. |
| ||
sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. |
|
* = Fields marked with an asterisk are mandatory.
1.2. Dependencies
At runtime, the aws-ddb-sink
Kamelet relies upon the presence of the following dependencies:
- mvn:org.apache.camel.kamelets:camel-kamelets-utils
- camel:core
- camel:jackson
- camel:aws2-ddb
- camel:kamelet
1.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/aws-ddb-sink.kamelet.yaml
2. Avro Deserialize Action
Deserialize payload to Avro
2.1. Configuration Options
The following table summarizes the configuration options available for the avro-deserialize-action
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
schema * | Schema | The Avro schema to use during serialization (as single-line, using JSON format) |
|
| |
validate | Validate | Indicates if the content must be validated against the schema |
|
|
* = Fields marked with an asterisk are mandatory.
2.2. Dependencies
At runtime, the avro-deserialize-action
Kamelet relies upon the presence of the following dependencies:
- camel:kamelet
- camel:core
- camel:jackson-avro
2.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/avro-deserialize-action.kamelet.yaml
3. Avro Serialize Action
Serialize payload to Avro
3.1. Configuration Options
The following table summarizes the configuration options available for the avro-serialize-action
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
schema * | Schema | The Avro schema to use during serialization (as single-line, using JSON format) |
|
| |
validate | Validate | Indicates if the content must be validated against the schema |
|
|
* = Fields marked with an asterisk are mandatory.
3.2. Dependencies
At runtime, the avro-serialize-action
Kamelet relies upon the presence of the following dependencies:
- camel:kamelet
- camel:core
- camel:jackson-avro
3.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/avro-serialize-action.kamelet.yaml
4. AWS Kinesis Sink
Send data to AWS Kinesis.
The Kamelet expects the following header:
-
partition
/ce-partition
: to set the Kinesis partition key
If the header won’t be set the exchange ID will be used.
The Kamelet is also able to recognize the following header:
-
sequence-number
/ce-sequencenumber
: to set the Sequence number
This header is optional.
4.1. Configuration Options
The following table summarizes the configuration options available for the aws-kinesis-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
region * | AWS Region | The AWS region to connect to |
|
| |
stream * | Stream Name | The Kinesis stream that you want to access (needs to be created in advance) |
| ||
accessKey | Access Key | The access key obtained from AWS |
| ||
secretKey | Secret Key | The secret key obtained from AWS |
| ||
useDefaultCredentialsProvider | Default Credentials Provider | If true, the Kinesis client loads credentials through a default credentials provider. If false, it uses the basic authentication method (access key and secret key). |
|
| |
useProfileCredentialsProvider | Profile Credentials Provider | Set whether the Kinesis client should expect to load credentials through a profile credentials provider. |
|
| |
useSessionCredentials | Session Credentials | Set whether the Kinesis client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in Kinesis. |
|
| |
profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter will set the profile name. |
| ||
sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. |
| ||
uriEndpointOverride | Overwrite Endpoint URI |
The overriding endpoint URI. To use this option, you must also select the |
| ||
overrideEndpoint | Endpoint Overwrite |
Select this option to override the endpoint URI. To use this option, you must also provide a URI for the |
|
|
* = Fields marked with an asterisk are mandatory.
4.2. Dependencies
At runtime, the aws-kinesis-sink
Kamelet relies upon the presence of the following dependencies:
- camel:aws2-kinesis
- camel:kamelet
- camel:core
4.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/aws-kinesis-sink.kamelet.yaml
5. AWS Kinesis Source
Receive data from AWS Kinesis.
5.1. Configuration Options
The following table summarizes the configuration options available for the aws-kinesis-source
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
region * | AWS Region | The AWS region to connect to |
|
| |
stream * | Stream Name | The Kinesis stream that you want to access (needs to be created in advance) |
| ||
accessKey | Access Key | The access key obtained from AWS |
| ||
secretKey | Secret Key | The secret key obtained from AWS |
| ||
useDefaultCredentialsProvider | Default Credentials Provider | If true, the Kinesis client loads credentials through a default credentials provider. If false, it uses the basic authentication method (access key and secret key). |
|
| |
useProfileCredentialsProvider | Profile Credentials Provider | Set whether the Kinesis client should expect to load credentials through a profile credentials provider. |
|
| |
useSessionCredentials | Session Credentials | Set whether the Kinesis client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in Kinesis. |
|
| |
profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter will set the profile name. |
| ||
sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. |
| ||
uriEndpointOverride | Overwrite Endpoint URI |
The overriding endpoint URI. To use this option, you must also select the |
| ||
overrideEndpoint | Endpoint Overwrite |
Select this option to override the endpoint URI. To use this option, you must also provide a URI for the |
|
| |
delay | Delay | The number of milliseconds before the next poll of the selected stream. |
|
| |
asyncClient | Async Client | If we want to a KinesisAsyncClient instance set it to true. |
|
| |
useKclConsumers | KCL Consumer | If we want to a KCL Consumer set it to true |
|
|
* = Fields marked with an asterisk are mandatory.
5.2. Dependencies
At runtime, the aws-kinesis-source
Kamelet relies upon the presence of the following dependencies:
- camel:kamelet
- camel:aws2-kinesis
- mvn:org.apache.camel.kamelets:camel-kamelets-utils
- camel:core
5.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/aws-kinesis-source.kamelet.yaml
6. AWS Lambda Sink
Send a payload to an AWS Lambda function
6.1. Configuration Options
The following table summarizes the configuration options available for the aws-lambda-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
function * | Function Name | The Lambda Function name |
| ||
region * | AWS Region | The AWS region to connect to |
|
| |
accessKey | Access Key | The access key obtained from AWS |
| ||
secretKey | Secret Key | The secret key obtained from AWS |
| ` | |
useDefaultCredentialsProvider | Default Credentials Provider | If true, the Lambda client loads credentials through a default credentials provider. If false, it uses the basic authentication method (access key and secret key). |
|
| |
useProfileCredentialsProvider | Profile Credentials Provider | Set whether the Lambda client should expect to load credentials through a profile credentials provider. |
|
| |
useSessionCredentials | Session Credentials | Set whether the Lambda client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in Lambda. |
|
| |
profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter will set the profile name. |
|
* = Fields marked with an asterisk are mandatory.
6.2. Dependencies
At runtime, the aws-lambda-sink
Kamelet relies upon the presence of the following dependencies:
- camel:kamelet
- camel:aws2-lambda
6.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/aws-lambda-sink.kamelet.yaml
7. AWS Redshift Sink
Send data to an AWS Redshift Database.
This Kamelet expects a JSON as body. The mapping between the JSON fields and parameters is done by key, so if you have the following query:
INSERT INTO accounts (username,city) VALUES (:#username,:#city)
The Kamelet needs to receive as input something like:
{ "username":"oscerd", "city":"Rome"}
7.1. Configuration Options
The following table summarizes the configuration options available for the aws-redshift-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
databaseName * | Database Name | The Database Name we are pointing |
| ||
query * | Query | The Query to execute against the AWS Redshift Database |
|
| |
serverName * | Server Name | Server Name for the data source |
|
| |
username | Username | The username to use for accessing a secured AWS Redshift Database |
| ||
password | Password | The password to use for accessing a secured AWS Redshift Database |
| ||
serverPort | Server Port | Server Port for the data source | string |
|
* = Fields marked with an asterisk are mandatory.
7.2. Dependencies
At runtime, the aws-redshift-sink
Kamelet relies upon the presence of the following dependencies:
- camel:jackson
- camel:kamelet
- camel:sql
- mvn:com.amazon.redshift:redshift-jdbc42:2.1.0.30
- mvn:org.apache.commons:commons-dbcp2:2.12.0.redhat-00001
7.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/aws-redshift-sink.kamelet.yaml
8. AWS SNS Sink
Send message to an AWS SNS Topic
8.1. Configuration Options
The following table summarizes the configuration options available for the aws-sns-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
region * | AWS Region | The AWS region to connect to |
|
| |
topicNameOrArn * | Topic Name | The SQS Topic name or ARN |
| ||
accessKey | Access Key | The access key obtained from AWS |
| ||
secretKey | Secret Key | The secret key obtained from AWS |
| ||
autoCreateTopic | Autocreate Topic | Setting the autocreation of the SNS topic. |
|
| |
useDefaultCredentialsProvider | Default Credentials Provider | If true, the SNS client loads credentials through a default credentials provider. If false, it uses the basic authentication method (access key and secret key). |
|
| |
useProfileCredentialsProvider | Profile Credentials Provider | Set whether the SNS client should expect to load credentials through a profile credentials provider. |
|
| |
useSessionCredentials | Session Credentials | Set whether the SNS client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in SNS. |
|
| |
profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter will set the profile name. |
| ||
sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. |
| ||
uriEndpointOverride | Overwrite Endpoint URI |
The overriding endpoint URI. To use this option, you must also select the |
| ||
overrideEndpoint | Endpoint Overwrite |
Select this option to override the endpoint URI. To use this option, you must also provide a URI for the |
|
|
* = Fields marked with an asterisk are mandatory.
8.2. Dependencies
At runtime, the aws-sns-sink
Kamelet relies upon the presence of the following dependencies:
- camel:kamelet
- camel:core
- camel:aws2-sns
8.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/aws-sns-sink.kamelet.yaml
9. AWS SQS Sink
Send message to an AWS SQS Queue
9.1. Configuration Options
The following table summarizes the configuration options available for the aws-sqs-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
queueNameOrArn * | Queue Name | The SQS Queue name or ARN |
| ||
region * | AWS Region | The AWS region to connect to |
|
| |
accessKey | Access Key | The access key obtained from AWS |
| ||
secretKey | Secret Key | The secret key obtained from AWS |
| ||
autoCreateQueue | Autocreate Queue | Setting the autocreation of the SQS queue. |
|
| |
amazonAWSHost | AWS Host | The hostname of the Amazon AWS cloud. |
|
| |
protocol | Protocol | The underlying protocol used to communicate with SQS. |
|
|
|
useDefaultCredentialsProvider | Default Credentials Provider | If true, the SQS client loads credentials through a default credentials provider. If false, it uses the basic authentication method (access key and secret key). |
|
| |
useProfileCredentialsProvider | Profile Credentials Provider | Set whether the SQS client should expect to load credentials through a profile credentials provider. |
|
| |
useSessionCredentials | Session Credentials | Set whether the SQS client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in SQS. |
|
| |
profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter will set the profile name. |
| ||
sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. |
| ||
uriEndpointOverride | Overwrite Endpoint URI |
The overriding endpoint URI. To use this option, you must also select the |
| ||
overrideEndpoint | Endpoint Overwrite |
Select this option to override the endpoint URI. To use this option, you must also provide a URI for the |
|
|
* = Fields marked with an asterisk are mandatory.
9.2. Dependencies
At runtime, the aws-sqs-sink
Kamelet relies upon the presence of the following dependencies:
- camel:core
- camel:aws2-sqs
- camel:kamelet
9.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/aws-sqs-sink.kamelet.yaml
10. AWS SQS Source
Receive data from AWS SQS.
10.1. Configuration Options
The following table summarizes the configuration options available for the aws-sqs-source
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
queueNameOrArn * | Queue Name | The SQS Queue name or ARN |
| ||
region * | AWS Region | The AWS region to connect to |
|
| |
accessKey | Access Key | The access key obtained from AWS |
| ||
secretKey | Secret Key | The secret key obtained from AWS |
| ||
autoCreateQueue | Autocreate Queue | Setting the autocreation of the SQS queue. |
|
| |
deleteAfterRead | Auto-delete Messages | Delete messages after consuming them |
|
| |
autoCreateQueue | Autocreate Queue | Setting the autocreation of the SQS queue. |
|
| |
amazonAWSHost | AWS Host | The hostname of the Amazon AWS cloud. |
|
| |
protocol | Protocol | The underlying protocol used to communicate with SQS |
|
|
|
queueURL | Queue URL | The full SQS Queue URL (required if using KEDA) |
| ||
useDefaultCredentialsProvider | Default Credentials Provider | If true, the SQS client loads credentials through a default credentials provider. If false, it uses the basic authentication method (access key and secret key). |
|
| |
useProfileCredentialsProvider | Profile Credentials Provider | Set whether the SQS client should expect to load credentials through a profile credentials provider. |
|
| |
useSessionCredentials | Session Credentials | Set whether the SQS client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in SQS. |
|
| |
profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter will set the profile name. |
| ||
sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. |
| ||
uriEndpointOverride | Overwrite Endpoint URI |
The overriding endpoint URI. To use this option, you must also select the |
| ||
overrideEndpoint | Endpoint Overwrite |
Select this option to override the endpoint URI. To use this option, you must also provide a URI for the |
|
| |
delay | Delay | The number of milliseconds before the next poll of the selected stream |
|
| |
greedy | Greedy Scheduler | If greedy is enabled, then the polling will happen immediately again, if the previous run polled 1 or more messages. |
|
| |
maxMessagesPerPoll | Max Messages Per Poll | The maximum number of messages to return. Amazon SQS never returns more messages than this value (however, fewer messages might be returned). Valid values 1 to 10. Default 1. |
|
| |
waitTimeSeconds | Wait Time Seconds | The duration (in seconds) for which the call waits for a message to arrive in the queue before returning. If a message is available, the call returns sooner than WaitTimeSeconds. If no messages are available and the wait time expires, the call does not return a message list. |
|
| |
visibilityTimeout | Visibility Timeout | The duration (in seconds) that the received messages are hidden from subsequent retrieve requests after being retrieved by a ReceiveMessage request. |
|
|
* = Fields marked with an asterisk are mandatory.
10.2. Dependencies
At runtime, the aws-sqs-source
Kamelet relies upon the presence of the following dependencies:
- mvn:org.apache.camel.kamelets:camel-kamelets-utils
- camel:aws2-sqs
- camel:core
- camel:kamelet
10.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/aws-sqs-source.kamelet.yaml
11. AWS SQS FIFO Sink
Send message to an AWS SQS FIFO Queue
11.1. Configuration Options
The following table summarizes the configuration options available for the aws-sqs-fifo-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
queueNameOrArn * | Queue Name | The SQS Queue name or ARN |
| ||
region * | AWS Region | The AWS region to connect to |
|
| |
accessKey | Access Key | The access key obtained from AWS |
| ||
secretKey | Secret Key | The secret key obtained from AWS |
| ||
autoCreateQueue | Autocreate Queue | Setting the autocreation of the SQS queue. |
|
| |
contentBasedDeduplication | Content-Based Deduplication | Use content-based deduplication (should be enabled in the SQS FIFO queue first) |
|
| |
contentBasedDeduplication | Content-Based Deduplication | Use content-based deduplication (should be enabled in the SQS FIFO queue first) | boolean |
| |
autoCreateQueue | Autocreate Queue | Setting the autocreation of the SQS queue. | boolean |
| |
amazonAWSHost | AWS Host | The hostname of the Amazon AWS cloud. | string |
| |
protocol | Protocol | The underlying protocol used to communicate with SQS | string |
|
|
useDefaultCredentialsProvider | Default Credentials Provider | Set whether the SQS client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | boolean |
| |
useProfileCredentialsProvider | Profile Credentials Provider | Set whether the SQS client should expect to load credentials through a profile credentials provider. | boolean |
| |
useSessionCredentials | Session Credentials | Set whether the SQS client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in SQS. | boolean |
| |
profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter will set the profile name. | string | ||
sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. | string | password | |
uriEndpointOverride | Overwrite Endpoint URI |
The overriding endpoint URI. To use this option, you must also select the | string | ||
overrideEndpoint | Endpoint Overwrite |
Select this option to override the endpoint URI. To use this option, you must also provide a URI for the | boolean |
|
* = Fields marked with an asterisk are mandatory.
11.2. Dependencies
At runtime, the aws-sqs-fifo-sink
Kamelet relies upon the presence of the following dependencies:
- camel:aws2-sqs
- camel:core
- camel:kamelet
11.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/aws-sqs-fifo-sink.kamelet.yaml
12. AWS S3 Sink
Upload data to AWS S3.
The Kamelet expects the following headers to be set:
-
file
/ce-file
: as the file name to upload
If the header won’t be set the exchange ID will be used as file name.
12.1. Configuration Options
The following table summarizes the configuration options available for the aws-s3-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
bucketNameOrArn * | Bucket Name | The S3 Bucket name or ARN. |
| ||
region * | AWS Region | The AWS region to connect to. |
|
| |
accessKey | Access Key | The access key obtained from AWS. |
| ||
secretKey | Secret Key | The secret key obtained from AWS. |
| ||
autoCreateBucket | Autocreate Bucket | Setting the autocreation of the S3 bucket bucketName. |
|
| |
useDefaultCredentialsProvider | Default Credentials Provider | If true, the S3 client loads credentials through a default credentials provider. If false, it uses the basic authentication method (access key and secret key). | boolean |
| |
useProfileCredentialsProvider | Profile Credentials Provider | Set whether the S3 client should expect to load credentials through a profile credentials provider. | boolean |
| |
useSessionCredentials | Session Credentials | Set whether the S3 client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in S3. | boolean |
| |
profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter will set the profile name. | string | ||
sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. | string | password | |
uriEndpointOverride | Overwrite Endpoint URI |
` The overriding endpoint URI. To use this option, you must also select the | string | ||
overrideEndpoint | Endpoint Overwrite |
Select this option to override the endpoint URI. To use this option, you must also provide a URI for the | boolean |
| |
forcePathStyle | Force Path Style | Forces path style when accessing AWS S3 buckets. | boolean |
| |
keyName | Key Name | The key name for saving an element in the bucket. | string |
* = Fields marked with an asterisk are mandatory.
12.2. Dependencies
At runtime, the aws-s3-sink
Kamelet relies upon the presence of the following dependencies:
- camel:aws2-s3
- camel:kamelet
12.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/aws-s3-sink.kamelet.yaml
13. AWS S3 Source
Receive data from AWS S3.
13.1. Configuration Options
The following table summarizes the configuration options available for the aws-s3-source
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
bucketNameOrArn * | Bucket Name | The S3 Bucket name or ARN |
| ||
region * | AWS Region | The AWS region to connect to |
|
| |
accessKey | Access Key | The access key obtained from AWS |
| ||
secretKey | Secret Key | The secret key obtained from AWS |
| ||
autoCreateBucket | Autocreate Bucket | Setting the autocreation of the S3 bucket bucketName. |
|
| |
deleteAfterRead | Auto-delete Objects | Delete objects after consuming them |
|
| |
moveAfterRead | Move Objects After Delete | Move objects from S3 bucket to a different bucket after they have been retrieved. | boolean |
| |
destinationBucket | Destination Bucket | Define the destination bucket where an object must be moved when moveAfterRead is set to true. | string | ||
destinationBucketPrefix | Destination Bucket Prefix | Define the destination bucket prefix to use when an object must be moved, and moveAfterRead is set to true. | string | ||
destinationBucketSuffix | Destination Bucket Suffix | Define the destination bucket suffix to use when an object must be moved, and moveAfterRead is set to true. | string | ||
accessKey | Access Key | The access key obtained from AWS. | string | password | |
secretKey | Secret Key | The secret key obtained from AWS. | string | password | |
autoCreateBucket | Autocreate Bucket | Specifies to automatically create the S3 bucket. | boolean |
| |
prefix | Prefix | The AWS S3 bucket prefix to consider while searching. | string |
| |
ignoreBody | Ignore Body |
If true, the S3 Object body is ignored. Setting this to true overrides any behavior defined by the | boolean |
| |
useDefaultCredentialsProvider | Default Credentials Provider | If true, the S3 client loads credentials through a default credentials provider. If false, it uses the basic authentication method (access key and secret key). | boolean |
| |
useProfileCredentialsProvider | Profile Credentials Provider | Set whether the S3 client should expect to load credentials through a profile credentials provider. | boolean |
| |
useSessionCredentials | Session Credentials | Set whether the S3 client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in S3. | boolean |
| |
profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter will set the profile name. | string | ||
sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. | string | password | |
uriEndpointOverride | Overwrite Endpoint URI |
` The overriding endpoint URI. To use this option, you must also select the | string | ||
overrideEndpoint | Endpoint Overwrite |
Select this option to override the endpoint URI. To use this option, you must also provide a URI for the | boolean |
| |
forcePathStyle | Force Path Style | Forces path style when accessing AWS S3 buckets. | boolean |
| |
delay | Delay | The number of milliseconds before the next poll of the selected bucket. | integer |
| |
maxMessagesPerPoll | Max Messages Per Poll | Gets the maximum number of messages as a limit to poll at each polling. Gets the maximum number of messages as a limit to poll at each polling. The default value is 10. Use 0 or a negative number to set it as unlimited. | integer |
|
* = Fields marked with an asterisk are mandatory.
13.2. Dependencies
At runtime, the aws-s3-source
Kamelet relies upon the presence of the following dependencies:
- camel:kamelet
- camel:aws2-s3
- camel:core
- mvn:org.apache.camel.kamelets:camel-kamelets-utils
13.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/aws-s3-source.kamelet.yaml
14. AWS S3 Streaming upload Sink
Upload data to AWS S3 in streaming upload mode.
14.1. Configuration Options
The following table summarizes the configuration options available for the aws-s3-streaming-upload-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
accessKey | Access Key | The access key obtained from AWS. |
| ||
bucketNameOrArn * | Bucket Name | The S3 Bucket name or ARN. |
| ||
keyName * | Key Name | Setting the key name for an element in the bucket through endpoint parameter. In Streaming Upload, with the default configuration, this will be the base for the progressive creation of files. |
| ||
region * | AWS Region | The AWS region to connect to. |
|
| |
secretKey | Secret Key | The secret key obtained from AWS. |
| ||
autoCreateBucket | Autocreate Bucket | Setting the autocreation of the S3 bucket bucketName. |
|
| |
autoCreateBucket | Autocreate Bucket | Setting the autocreation of the S3 bucket bucketName. | boolean |
| |
restartingPolicy | Restarting Policy | The restarting policy to use in streaming upload mode. There are 2 enums and the value can be one of override, lastPart | string |
| |
batchMessageNumber | Batch Message Number | The number of messages composing a batch in streaming upload mode | integer |
| |
batchSize | Batch Size | The batch size (in bytes) in streaming upload mode | integer |
| |
streamingUploadTimeout | Streaming Upload Timeout | While streaming upload mode is true, this option set the timeout to complete upload | integer | ||
namingStrategy | Naming Strategy | The naming strategy to use in streaming upload mode. There are 2 enums and the value can be one of progressive, random | string | "progressive" | |
keyName | Key Name | Setting the key name for an element in the bucket through endpoint parameter. In Streaming Upload, with the default configuration, this will be the base for the progressive creation of files. | string | ||
useDefaultCredentialsProvider | Default Credentials Provider | Set whether the S3 client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | boolean |
| |
useProfileCredentialsProvider | Profile Credentials Provider | Set whether the S3 client should expect to load credentials through a profile credentials provider. | boolean |
| |
useSessionCredentials | Session Credentials | Set whether the S3 client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in S3. | boolean |
| |
profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter will set the profile name. | string | ||
sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. | string | password | |
uriEndpointOverride | Overwrite Endpoint URI |
The overriding endpoint URI. To use this option, you must also select the | string | ||
overrideEndpoint | Endpoint Overwrite |
Select this option to override the endpoint URI. To use this option, you must also provide a URI for the | boolean |
| |
forcePathStyle | Force Path Style | Forces path style when accessing AWS S3 buckets. | boolean |
|
* = Fields marked with an asterisk are mandatory.
14.2. Dependencies
At runtime, the aws-s3-streaming-upload-sink
Kamelet relies upon the presence of the following dependencies:
- camel:aws2-s3
- camel:kamelet
14.3. Kamelets source file
15. Cassandra Sink
Send data to a Cassandra Cluster.
This Kamelet expects the body as JSON Array. The content of the JSON Array will be used as input for the CQL Prepared Statement set in the query parameter.
15.1. Configuration Options
The following table summarizes the configuration options available for the cassandra-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
connectionHost * | Connection Host | Hostname(s) cassandra server(s). Multiple hosts can be separated by comma. |
|
| |
connectionPort * | Connection Port | Port number of cassandra server(s) |
|
| |
keyspace * | Keyspace | Keyspace to use |
|
| |
query * | Query | The query to execute against the Cassandra cluster table |
| ||
password | Password | The password to use for accessing a secured Cassandra Cluster |
| ||
username | Username | The username to use for accessing a secured Cassandra Cluster |
| ||
consistencyLevel | Consistency Level | Consistency level to use. The value can be one of ANY, ONE, TWO, THREE, QUORUM, ALL, LOCAL_QUORUM, EACH_QUORUM, SERIAL, LOCAL_SERIAL, LOCAL_ONE | string |
| |
prepareStatements | Prepare Statements | If true, specifies to use PreparedStatements as the query. If false, specifies to use regular Statements as the query. | boolean |
| |
extraTypeCodecs | Extra Type Codecs | To use a specific comma separated list of Extra Type codecs. | string |
| |
jsonPayload | JSON Payload | If we want to transform the payload in json or not | boolean |
|
* = Fields marked with an asterisk are mandatory.
15.2. Dependencies
At runtime, the cassandra-sink
Kamelet relies upon the presence of the following dependencies:
- camel:jackson
- camel:kamelet
- camel:cassandraql
- camel:core
15.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/cassandra-sink.kamelet.yaml
16. Cassandra Source
Query a Cassandra cluster table.
16.1. Configuration Options
The following table summarizes the configuration options available for the cassandra-source
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
connectionHost * | Connection Host | Hostname(s) cassandra server(s). Multiple hosts can be separated by comma. |
|
| |
connectionPort * | Connection Port | Port number of cassandra server(s) |
|
| |
keyspace * | Keyspace | Keyspace to use |
|
| |
query * | Query | The query to execute against the Cassandra cluster table |
| ||
password | Password | The password to use for accessing a secured Cassandra Cluster |
| ||
username | Username | The username to use for accessing a secured Cassandra Cluster |
| ||
consistencyLevel | Consistency Level | Consistency level to use. The value can be one of ANY, ONE, TWO, THREE, QUORUM, ALL, LOCAL_QUORUM, EACH_QUORUM, SERIAL, LOCAL_SERIAL, LOCAL_ONE | string |
| |
resultStrategy | Result Strategy | The strategy to convert the result set of the query. Possible values are ALL, ONE, LIMIT_10, LIMIT_100… | string |
| |
extraTypeCodecs | Extra Type Codecs | To use a specific comma separated list of Extra Type codecs. | string |
|
* = Fields marked with an asterisk are mandatory.
16.2. Dependencies
At runtime, the cassandra-source
Kamelet relies upon the presence of the following dependencies:
- camel:jackson
- camel:kamelet
- camel:cassandraql
16.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/cassandra-source.kamelet.yaml
17. Ceph Sink
Upload data to an Ceph Bucket managed by a Object Storage Gateway.
In the header, you can optionally set the file
/ ce-file
property to specify the name of the file to upload.
If you do not set the property in the header, the Kamelet uses the exchange ID for the file name.
17.1. Configuration Options
The following table summarizes the configuration options available for the ceph-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
bucketName * | Bucket Name | The Ceph Bucket name. |
| ||
cephUrl * | Ceph Url Address | Set the Ceph Object Storage Address Url. |
|
| |
zoneGroup * | Bucket Zone Group | The bucket zone group. |
| ||
accessKey | Access Key | The access key. |
| ||
secretKey | Secret Key | The secret key. |
| ||
autoCreateBucket | Autocreate Bucket | Specifies to automatically create the bucket. |
|
| |
keyName | Key Name | The key name for saving an element in the bucket. |
|
* = Fields marked with an asterisk are mandatory.
17.2. Dependencies
At runtime, the ceph-sink
Kamelet relies upon the presence of the following dependencies:
- camel:core
- camel:aws2-s3
- camel:kamelet
17.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/ceph-sink.kamelet.yaml
18. Ceph Source
Receive data from an Ceph Bucket, managed by a Object Storage Gateway.
18.1. Configuration Options
The following table summarizes the configuration options available for the ceph-source
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
bucketName * | Bucket Name | The Ceph Bucket name. |
| ||
cephUrl * | Ceph Url Address | Set the Ceph Object Storage Address Url. |
|
| |
zoneGroup * | Bucket Zone Group | The bucket zone group. |
| ||
accessKey | Access Key | The access key. |
| ||
secretKey | Secret Key | The secret key. |
| ||
autoCreateBucket | Autocreate Bucket | Specifies to automatically create the bucket. |
|
| |
delay | Delay | The number of milliseconds before the next poll of the selected bucket. | integer |
| |
deleteAfterRead | Auto-delete Objects | Specifies to delete objects after consuming them. |
|
| |
ignoreBody | Ignore Body |
If true, the Object body is ignored. Setting this to true overrides any behavior defined by the |
|
| |
includeBody | Include Body | If true, the exchange is consumed and put into the body and closed. If false, the Object stream is put raw into the body and the headers are set with the object metadata. |
|
| |
prefix | Prefix | The bucket prefix to consider while searching. |
|
|
* = Fields marked with an asterisk are mandatory.
18.2. Dependencies
At runtime, the ceph-source
Kamelet relies upon the presence of the following dependencies:
- camel:aws2-s3
- camel:kamelet
18.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/ceph-source.kamelet.yaml
19. Extract Field Action
Extract a field from the body
19.1. Configuration Options
The following table summarizes the configuration options available for the extract-field-action
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
field * | Field | The name of the field to be added |
| ||
headerOutput | Header Output | If enable the action will store the extracted field in an header named CamelKameletsExtractFieldName |
|
| |
headerOutputName | Header Output Name | A custom name for the header containing the extracted field |
|
| |
strictHeaderCheck | 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). |
|
| |
trimField | Trim Field | If enabled we return the Raw extracted field |
|
|
* = Fields marked with an asterisk are mandatory.
19.2. Dependencies
At runtime, the extract-field-action
Kamelet relies upon the presence of the following dependencies:
- mvn:org.apache.camel.kamelets:camel-kamelets-utils
- camel:kamelet
- camel:core
- camel:jackson
19.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/extract-field-action.kamelet.yaml
20. FTP Sink
Send data to an FTP Server.
The Kamelet expects the following headers to be set:
-
file
/ce-file
: as the file name to upload
If the header won’t be set the exchange ID will be used as file name.
20.1. Configuration Options
The following table summarizes the configuration options available for the ftp-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
connectionHost * | Connection Host | Hostname of the FTP server |
| ||
connectionPort * | Connection Port | Port of the FTP server | string |
| |
directoryName * | Directory Name | The starting directory |
| ||
password | Password | The password to access the FTP server |
| ||
username | Username | The username to access the FTP server |
| ||
fileExist | File Existence | How to behave in case of file already existent. There are 4 enums and the value can be one of Override, Append, Fail or Ignore | string |
| |
passiveMode | Passive Mode | Sets passive mode connection |
|
| |
binary | Binary | Specifies the file transfer mode, BINARY or ASCII. Default is ASCII (false). | boolean |
| |
autoCreate | Autocreate Missing Directories | Automatically create starting directory. | boolean |
| |
delete | Delete | If true, the file will be deleted after it is processed successfully. | boolean |
|
* = Fields marked with an asterisk are mandatory.
20.2. Dependencies
At runtime, the ftp-sink
Kamelet relies upon the presence of the following dependencies:
- camel:ftp
- camel:core
- camel:kamelet
20.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/ftp-sink.kamelet.yaml
21. FTP Source
Receive data from an FTP Server.
21.1. Configuration Options
The following table summarizes the configuration options available for the ftp-source
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
connectionHost * | Connection Host | Hostname of the FTP server |
| ||
connectionPort * | Connection Port | Port of the FTP server | string |
| |
directoryName * | Directory Name | The starting directory |
| ||
password | Password | The password to access the FTP server |
| ||
username | Username | The username to access the FTP server |
| ||
idempotent | Idempotency | Skip already processed files. |
|
| |
passiveMode | Passive Mode | Sets passive mode connection |
|
| |
recursive | Recursive | If a directory, will look for files in all the subdirectories as well. |
|
| |
binary | Binary | Specifies the file transfer mode, BINARY or ASCII. Default is ASCII (false). | boolean |
| |
autoCreate | Autocreate Missing Directories | Automatically create starting directory. | boolean |
| |
delete | Delete | If true, the file will be deleted after it is processed successfully. | boolean |
|
* = Fields marked with an asterisk are mandatory.
21.2. Dependencies
At runtime, the ftp-source
Kamelet relies upon the presence of the following dependencies:
- camel:ftp
- camel:core
- camel:kamelet
21.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/ftp-source.kamelet.yaml
22. FTPS Sink
Send data to an FTPS Server.
The Kamelet expects the following headers to be set:
-
file
/ce-file
: as the file name to upload
If the header won’t be set the exchange ID will be used as file name.
22.1. Configuration Options
The following table summarizes the configuration options available for the ftps-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
connectionHost * | Connection Host | Hostname of the FTP server |
| ||
connectionPort * | Connection Port | Port of the FTP server | string |
| |
directoryName * | Directory Name | The starting directory |
| ||
password | Password | The password to access the FTP server |
| ||
username | Username | The username to access the FTP server |
| ||
fileExist | File Existence | How to behave in case of file already existent. There are 4 enums and the value can be one of Override, Append, Fail or Ignore | string |
| |
passiveMode | Passive Mode | Sets passive mode connection |
|
| |
binary | Binary | Specifies the file transfer mode, BINARY or ASCII. Default is ASCII (false). | boolean |
| |
autoCreate | Autocreate Missing Directories | Automatically create starting directory. | boolean |
| |
delete | Delete | If true, the file will be deleted after it is processed successfully. | boolean |
|
* = Fields marked with an asterisk are mandatory.
22.2. Dependencies
At runtime, the ftps-sink
Kamelet relies upon the presence of the following dependencies:
- camel:ftp
- camel:core
- camel:kamelet
22.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/ftps-sink.kamelet.yaml
23. FTPS Source
Receive data from an FTPS Server.
23.1. Configuration Options
The following table summarizes the configuration options available for the ftps-source
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
connectionHost * | Connection Host | Hostname of the FTPS server |
| ||
connectionPort * | Connection Port | Port of the FTPS server | string |
| |
directoryName * | Directory Name | The starting directory |
| ||
password | Password | The password to access the FTPS server |
| ||
username | Username | The username to access the FTPS server |
| ||
idempotent | Idempotency | Skip already processed files. |
|
| |
passiveMode | Passive Mode | Sets passive mode connection |
|
| |
recursive | Recursive | If a directory, will look for files in all the subdirectories as well. |
|
| |
binary | Binary | Specifies the file transfer mode, BINARY or ASCII. Default is ASCII (false). | boolean |
| |
autoCreate | Autocreate Missing Directories | Automatically create starting directory. | boolean |
| |
delete | Delete | If true, the file will be deleted after it is processed successfully. | boolean |
|
* = Fields marked with an asterisk are mandatory.
23.2. Dependencies
At runtime, the ftps-source
Kamelet relies upon the presence of the following dependencies:
- camel:ftp
- camel:core
- camel:kamelet
23.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/ftps-source.kamelet.yaml
24. Has Header Filter Action
Filter based on the presence of one header
24.1. Configuration Options
The following table summarizes the configuration options available for the has-header-filter-action
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
name * | Header Name | The header name to evaluate. The header name must be passed by the source Kamelet. For Knative only, if you are using Cloud Events, you must include the CloudEvent (ce-) prefix in the header name. |
|
| |
value | Header Value | An optional header value to compare the header to. | string | headerValue |
* = Fields marked with an asterisk are mandatory.
24.2. Dependencies
At runtime, the has-header-filter-action
Kamelet relies upon the presence of the following dependencies:
- camel:core
- camel:kamelet
24.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/has-header-filter-action.kamelet.yaml
25. Hoist Field Action
Wrap data in a single field
25.1. Configuration Options
The following table summarizes the configuration options available for the hoist-field-action
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
field * | Field | The name of the field that will contain the event |
|
* = Fields marked with an asterisk are mandatory.
25.2. Dependencies
At runtime, the hoist-field-action
Kamelet relies upon the presence of the following dependencies:
- mvn:org.apache.camel.kamelets:camel-kamelets-utils
- camel:core
- camel:jackson
- camel:kamelet
25.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/hoist-field-action.kamelet.yaml
26. HTTP Sink
Forwards an event to a HTTP endpoint
26.1. Configuration Options
The following table summarizes the configuration options available for the http-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
url * | URL | The URL to send data to |
|
| |
method | Method | The HTTP method to use | string |
|
* = Fields marked with an asterisk are mandatory.
26.2. Dependencies
At runtime, the http-sink
Kamelet relies upon the presence of the following dependencies:
- camel:http
- camel:kamelet
- camel:core
26.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/http-sink.kamelet.yaml
27. Insert Field Action
Adds a custom field with a constant value to the message in transit
27.1. Configuration Options
The following table summarizes the configuration options available for the insert-field-action
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
field * | Field | The name of the field to be added |
| ||
value * | Value | The value of the field |
|
* = Fields marked with an asterisk are mandatory.
27.2. Dependencies
At runtime, the insert-field-action
Kamelet relies upon the presence of the following dependencies:
- mvn:org.apache.camel.kamelets:camel-kamelets-utils
- camel:core
- camel:jackson
- camel:kamelet
27.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/insert-field-action.kamelet.yaml
28. Insert Header Action
Adds an header with a constant value to the message in transit
28.1. Configuration Options
The following table summarizes the configuration options available for the insert-header-action
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
name * | Name | The name of the header to be added. For Knative only, the name of the header requires a CloudEvent (ce-) prefix. |
| ||
value * | Value | The value of the header |
|
* = Fields marked with an asterisk are mandatory*.
28.2. Dependencies
At runtime, the insert-header-action
Kamelet relies upon the presence of the following dependencies:
- camel:core
- camel:kamelet
28.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/insert-header-action.kamelet.yaml
29. Is Tombstone Filter Action
Filter based on the presence of body or not
29.1. Configuration Options
The is-tombstone-filter-action
Kamelet does not specify any configuration option.
29.2. Dependencies
At runtime, the is-tombstone-filter-action
Kamelet relies upon the presence of the following dependencies:
- camel:core
- camel:kamelet
29.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/is-tombstone-filter-action.kamelet.yaml
30. Jira Add Comment Sink
Add a new comment to an existing issue in Jira.
The Kamelet expects the following headers to be set:
-
issueKey
/ce-issueKey
: as the issue code.
The comment is set in the body of the message.
30.1. Configuration Options
The following table summarizes the configuration options available for the jira-add-comment-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
jiraUrl * | Jira URL | The URL of your instance of Jira |
|
| |
password | Password | The password or the API Token to access Jira |
| ||
username | Username | The username to access Jira |
| ||
personal-token | Personal Token | Personal Token | string |
* = Fields marked with an asterisk are mandatory.
30.2. Dependencies
At runtime, the jira-add-comment-sink
Kamelet relies upon the presence of the following dependencies:
- camel:core
- camel:jackson
- camel:jira
- camel:kamelet
- mvn:com.fasterxml.jackson.datatype:jackson-datatype-joda:2.12.4.redhat-00001
30.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/jira-add-comment-sink.kamelet.yaml
31. Jira Add Issue Sink
Add a new issue to Jira.
The Kamelet expects the following headers to be set:
-
projectKey
/ce-projectKey
: as the Jira project key. -
issueTypeName
/ce-issueTypeName
: as the name of the issue type (example: Bug, Enhancement). -
issueSummary
/ce-issueSummary
: as the title or summary of the issue. -
issueAssignee
/ce-issueAssignee
: as the user assigned to the issue (Optional). -
issuePriorityName
/ce-issuePriorityName
: as the priority name of the issue (example: Critical, Blocker, Trivial) (Optional). -
issueComponents
/ce-issueComponents
: as list of string with the valid component names (Optional). -
issueDescription
/ce-issueDescription
: as the issue description (Optional).
The issue description can be set from the body of the message or the issueDescription
/ce-issueDescription
in the header, however the body takes precedence.
31.1. Configuration Options
The following table summarizes the configuration options available for the jira-add-issue-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
jiraUrl * | Jira URL | The URL of your instance of Jira |
|
| |
password | Password | The password or the API Token to access Jira |
| ||
username | Username | The username to access Jira |
| ||
personal-token | Personal Token | Personal Token | string |
* = Fields marked with an asterisk are mandatory.
31.2. Dependencies
At runtime, the jira-add-issue-sink
Kamelet relies upon the presence of the following dependencies:
- camel:core
- camel:jackson
- camel:jira
- camel:kamelet
- mvn:com.fasterxml.jackson.datatype:jackson-datatype-joda:2.12.4.redhat-00001
31.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/jira-add-issue-sink.kamelet.yaml
32. Jira Transition Issue Sink
Sets a new status (transition to) of an existing issue in Jira.
The Kamelet expects the following headers to be set:
-
issueKey
/ce-issueKey
: as the issue unique code. -
issueTransitionId
/ce-issueTransitionId
: as the new status (transition) code. You should carefully check the project workflow as each transition may have conditions to check before the transition is made.
The comment of the transition is set in the body of the message.
32.1. Configuration Options
The following table summarizes the configuration options available for the jira-transition-issue-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
jiraUrl * | Jira URL | The URL of your instance of Jira |
|
| |
password | Password | The password or the API Token to access Jira |
| ||
username | Username | The username to access Jira |
| ||
personal-token | Personal Token | Personal Token | string |
* = Fields marked with an asterisk are mandatory.
32.2. Dependencies
At runtime, the jira-transition-issue-sink
Kamelet relies upon the presence of the following dependencies:
- camel:core
- camel:jackson
- camel:jira
- camel:kamelet
- mvn:com.fasterxml.jackson.datatype:jackson-datatype-joda:2.12.4.redhat-00001
32.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/jira-transition-issue-sink.kamelet.yaml
33. Jira Update Issue Sink
Update fields of an existing issue in Jira. The Kamelet expects the following headers to be set:
-
issueKey
/ce-issueKey
: as the issue code in Jira. -
issueTypeName
/ce-issueTypeName
: as the name of the issue type (example: Bug, Enhancement). -
issueSummary
/ce-issueSummary
: as the title or summary of the issue. -
issueAssignee
/ce-issueAssignee
: as the user assigned to the issue (Optional). -
issuePriorityName
/ce-issuePriorityName
: as the priority name of the issue (example: Critical, Blocker, Trivial) (Optional). -
issueComponents
/ce-issueComponents
: as list of string with the valid component names (Optional). -
issueDescription
/ce-issueDescription
: as the issue description (Optional).
The issue description can be set from the body of the message or the issueDescription
/ce-issueDescription
in the header, however the body takes precedence.
33.1. Configuration Options
The following table summarizes the configuration options available for the jira-update-issue-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
jiraUrl * | Jira URL | The URL of your instance of Jira |
|
| |
password | Password | The password or the API Token to access Jira |
| ||
username | Username | The username to access Jira |
| ||
personal-token | Personal Token | Personal Token | string |
* = Fields marked with an asterisk are mandatory.
33.2. Dependencies
At runtime, the jira-update-issue-sink
Kamelet relies upon the presence of the following dependencies:
- camel:core
- camel:jackson
- camel:jira
- camel:kamelet
- mvn:com.fasterxml.jackson.datatype:jackson-datatype-joda:2.12.4.redhat-00001
33.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/jira-update-issue-sink.kamelet.yaml
34. Jira Source
Receive notifications about new issues from Jira.
34.1. Configuration Options
The following table summarizes the configuration options available for the jira-source
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
jiraUrl * | Jira URL | The URL of your instance of Jira |
|
| |
password | Password | The password to access Jira |
| ||
username | Username | The username to access Jira |
| ||
jql | JQL | A query to filter issues |
|
| |
personal-token | Personal Token | Personal Token | string |
* = Fields marked with an asterisk are mandatory.
34.2. Dependencies
At runtime, the jira-source
Kamelet relies upon the presence of the following dependencies:
- camel:jackson
- camel:kamelet
- camel:jira
34.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/jira-source.kamelet.yaml
35. JMS - AMQP 1.0 Kamelet Sink
A Kamelet that can produce events to any AMQP 1.0 compliant message broker using the Apache Qpid JMS client
35.1. Configuration Options
The following table summarizes the configuration options available for the jms-amqp-10-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
destinationName * | Destination Name | The JMS destination name |
| ||
remoteURI * | Broker URL | The JMS URL |
|
| |
destinationType | Destination Type | The JMS destination type (i.e.: queue or topic) | string |
|
* = Fields marked with an asterisk are mandatory.
35.2. Dependencies
At runtime, the jms-amqp-10-sink
Kamelet relies upon the presence of the following dependencies:
- camel:jms
- camel:kamelet
- mvn:org.apache.qpid:qpid-jms-client:0.55.0
35.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/jms-amqp-10-sink.kamelet.yaml
36. JMS - AMQP 1.0 Source
A Kamelet that can consume events from any AMQP 1.0 compliant message broker using the Apache Qpid JMS client
36.1. Configuration Options
The following table summarizes the configuration options available for the jms-amqp-10-source
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
destinationName * | Destination Name | The JMS destination name |
| ||
remoteURI * | Broker URL | The JMS URL |
|
| |
destinationType | Destination Type | The JMS destination type (i.e.: queue or topic) | string |
|
* = Fields marked with an asterisk are mandatory.
36.2. Dependencies
At runtime, the jms-amqp-10-source
Kamelet relies upon the presence of the following dependencies:
- camel:jms
- camel:kamelet
36.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/jms-amqp-10-source.kamelet.yaml
37. JMS - IBM MQ Kamelet Sink
A Kamelet that can produce events to an IBM MQ message queue using JMS.
37.1. Configuration Options
The following table summarizes the configuration options available for the jms-ibm-mq-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
channel * | IBM MQ Channel | Name of the IBM MQ Channel |
| ||
destinationName * | Destination Name | The destination name |
| ||
queueManager * | IBM MQ Queue Manager | Name of the IBM MQ Queue Manager |
| ||
serverName * | IBM MQ Server name | IBM MQ Server name or address |
| ||
serverPort * | IBM MQ Server Port | IBM MQ Server port | integer |
| |
password | Password | Password to authenticate to IBM MQ server |
| ||
username | Username | Username to authenticate to IBM MQ server |
| ||
clientId | IBM MQ Client ID | Name of the IBM MQ Client ID |
| ||
destinationType | Destination Type | The JMS destination type (queue or topic) | string |
|
* = Fields marked with an asterisk are mandatory.
37.2. Dependencies
At runtime, the jms-ibm-mq-sink
Kamelet relies upon the presence of the following dependencies:
- camel:jms
- camel:kamelet
- mvn:com.ibm.mq:com.ibm.mq.allclient:9.2.5.0
37.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/jms-ibm-mq-sink.kamelet.yaml
38. JMS - IBM MQ Source
A Kamelet that can read events from an IBM MQ message queue using JMS.
38.1. Configuration Options
The following table summarizes the configuration options available for the jms-ibm-mq-source
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
channel * | IBM MQ Channel | Name of the IBM MQ Channel |
| ||
destinationName * | Destination Name | The destination name |
| ||
queueManager * | IBM MQ Queue Manager | Name of the IBM MQ Queue Manager |
| ||
serverName * | IBM MQ Server name | IBM MQ Server name or address |
| ||
serverPort * | IBM MQ Server Port | IBM MQ Server port | integer |
| |
password | Password | Password to authenticate to IBM MQ server |
| ||
username | Username | Username to authenticate to IBM MQ server |
| ||
clientId | IBM MQ Client ID | Name of the IBM MQ Client ID |
| ||
destinationType | Destination Type | The JMS destination type (queue or topic) | string |
| |
sslCipherSuite | CipherSuite | CipherSuite to use for enabling TLS | string |
* = Fields marked with an asterisk are mandatory.
38.2. Dependencies
At runtime, the jms-ibm-mq-source
Kamelet relies upon the presence of the following dependencies:
- camel:jms
- camel:kamelet
38.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/jms-ibm-mq-source.kamelet.yaml
39. JSLT Action
Apply a JSLT query or transformation on JSON.
39.1. Configuration Options
The following table summarizes the configuration options available for the jslt-action
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
template * | Template | The inline template for JSLT Transformation |
|
|
* = Fields marked with an asterisk are mandatory.
39.2. Dependencies
At runtime, the jslt-action
Kamelet relies upon the presence of the following dependencies:
- camel:jslt
- camel:kamelet
39.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/jslt-action.kamelet.yaml
40. Json Deserialize Action
Deserialize payload to JSON
40.1. Configuration Options
The json-deserialize-action
Kamelet does not specify any configuration option.
40.2. Dependencies
At runtime, the json-deserialize-action
Kamelet relies upon the presence of the following dependencies:
- mvn:org.apache.camel.kamelets:camel-kamelets-utils
- camel:kamelet
- camel:core
- camel:jackson
40.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/json-deserialize-action.kamelet.yaml
41. Json Serialize Action
Serialize payload to JSON
41.1. Configuration Options
The json-serialize-action
Kamelet does not specify any configuration option.
41.2. Dependencies
At runtime, the json-serialize-action
Kamelet relies upon the presence of the following dependencies:
- camel:kamelet
- camel:core
- camel:jackson
41.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/json-serialize-action.kamelet.yaml
42. Kafka Sink
Send data to Kafka topics.
The Kamelet is able to understand the following headers to be set:
-
key
/ce-key
: as message key -
partition-key
/ce-partitionkey
: as message partition key
Both the headers are optional.
42.1. Configuration Options
The following table summarizes the configuration options available for the kafka-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
bootstrapServers * | Brokers | Comma separated list of Kafka Broker URLs |
| ||
topic * | Topic Names | Comma separated list of Kafka topic names |
| ||
user * | Username | Username to authenticate to Kafka |
| ||
password | Password | Password to authenticate to kafka |
| ||
saslMechanism | SASL Mechanism | The Simple Authentication and Security Layer (SASL) Mechanism used. | string |
| |
securityProtocol | Security Protocol | Protocol used to communicate with brokers. SASL_PLAINTEXT, PLAINTEXT, SASL_SSL and SSL are supported | string |
|
* = Fields marked with an asterisk are mandatory.
42.2. Dependencies
At runtime, the `kafka-sink Kamelet relies upon the presence of the following dependencies:
- camel:kafka
- camel:kamelet
- camel:core
42.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/kafka-sink.kamelet.yaml
43. Kafka Source
Receive data from Kafka topics.
43.1. Configuration Options
The following table summarizes the configuration options available for the kafka-source
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
topic * | Topic Names | Comma separated list of Kafka topic names |
| ||
bootstrapServers * | Brokers | Comma separated list of Kafka Broker URLs |
| ||
user * | Username | Username to authenticate to Kafka |
| ||
password * | Password | Password to authenticate to kafka |
| ||
securityProtocol | Security Protocol | Protocol used to communicate with brokers. SASL_PLAINTEXT, PLAINTEXT, SASL_SSL and SSL are supported | string |
| |
saslMechanism | SASL Mechanism | The Simple Authentication and Security Layer (SASL) Mechanism used. | string |
| |
autoCommitEnable | Auto Commit Enable | If true, periodically commit to ZooKeeper the offset of messages already fetched by the consumer. |
|
| |
allowManualCommit | Allow Manual Commit | Whether to allow doing manual commits |
|
| |
autoOffsetReset | Auto Offset Reset | What to do when there is no initial offset. There are 3 enums and the value can be one of latest, earliest, none | string |
| |
pollOnError | Poll On Error Behavior | What to do if kafka threw an exception while polling for new messages. There are 5 enums and the value can be one of DISCARD, ERROR_HANDLER, RECONNECT, RETRY, STOP | string |
| |
deserializeHeaders | Automatically Deserialize Headers |
When enabled the Kamelet source will deserialize all message headers to String representation. The default is |
|
| |
consumerGroup | Consumer Group | A string that uniquely identifies the group of consumers to which this source belongs | string | "my-group-id" | |
topicIsPattern | Topic Is Pattern | Whether the topic is a pattern (regular expression). This can be used to subscribe to dynamic number of topics matching the pattern. | boolean |
|
* = Fields marked with an asterisk are mandatory.
43.2. Dependencies
At runtime, the `kafka-source Kamelet relies upon the presence of the following dependencies:
- mvn:org.apache.camel.kamelets:camel-kamelets-utils
- camel:kafka
- camel:kamelet
- camel:core
43.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/kafka-source.kamelet.yaml
44. Kafka Topic Name Matches Filter Action
Filter based on kafka topic value compared to regex
44.1. Configuration Options
The following table summarizes the configuration options available for the topic-name-matches-filter-action
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
regex * | Regex | The Regex to Evaluate against the Kafka topic name |
|
* = Fields marked with an asterisk are mandatory.
44.2. Dependencies
At runtime, the topic-name-matches-filter-action
Kamelet relies upon the presence of the following dependencies:
- camel:core
- camel:kamelet
44.3. Kamelets source file
45. Log Sink
A sink that logs all data that it receives, useful for debugging purposes.
45.1. Configuration Options
The following table summarizes the configuration options available for the log-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
loggerName | Logger Name | Name of the logging category to use |
|
| |
level | Log Level | Logging level to use |
|
|
|
logMask | Log Mask | Mask sensitive information like password or passphrase in the log |
|
| |
marker | Marker | An optional Marker name to use |
| ||
multiline | Multiline | If enabled then each information is outputted on a newline |
|
| |
showAllProperties | Show All Properties | Show all of the exchange properties (both internal and custom) |
|
| |
showBody | Show Body | Show the message body |
|
| |
showBodyType | Show Body Type | Show the body Java type |
|
| |
showExchangePattern | Show Exchange Pattern | Shows the Message Exchange Pattern (or MEP for short) |
|
| |
showHeaders | Show Headers | Show the headers received |
|
| |
showProperties | Show Properties | Show the exchange properties (only custom). Use showAllProperties to show both internal and custom properties. |
|
| |
showStreams | Show Streams | Show the stream bodies (they may not be available in following steps) |
|
| |
showCachedStreams | Show Cached Streams | Whether Camel should show cached stream bodies or not. |
|
|
* = Fields marked with an asterisk are mandatory.
45.2. Dependencies
At runtime, the log-sink
Kamelet relies upon the presence of the following dependencies:
- camel:kamelet
- camel:log
45.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/log-sink.kamelet.yaml
46. MariaDB Sink
Send data to a MariaDB Database.
This Kamelet expects a JSON as body. The mapping between the JSON fields and parameters is done by key, so if you have the following query:
'INSERT INTO accounts (username,city) VALUES (:#username,:#city)'
The Kamelet needs to receive as input something like:
'{ "username":"oscerd", "city":"Rome"}'
46.1. Configuration Options
The following table summarizes the configuration options available for the mariadb-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
databaseName * | Database Name | The Database Name we are pointing |
| ||
query * | Query | The Query to execute against the MariaDB Database |
|
| |
serverName * | Server Name | Server Name for the data source |
|
| |
password | Password | The password to use for accessing a secured MariaDB Database |
| ||
username | Username | The username to use for accessing a secured MariaDB Database |
| ||
serverPort | Server Port | Server Port for the data source | string |
|
* = Fields marked with an asterisk are mandatory.
46.2. Dependencies
At runtime, the mariadb-sink
Kamelet relies upon the presence of the following dependencies:
- camel:jackson
- camel:kamelet
- camel:sql
- mvn:org.apache.commons:commons-dbcp2:2.12.0.redhat-00001
- mvn:org.mariadb.jdbc:mariadb-java-client
46.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/mariadb-sink.kamelet.yaml
47. Mask Fields Action
Mask fields with a constant value in the message in transit
47.1. Configuration Options
The following table summarizes the configuration options available for the mask-field-action
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
fields * | Fields | Comma separated list of fields to mask |
| ||
replacement * | Replacement | Replacement for the fields to be masked |
|
* = Fields marked with an asterisk are mandatory.
47.2. Dependencies
At runtime, the mask-field-action
Kamelet relies upon the presence of the following dependencies:
- mvn:org.apache.camel.kamelets:camel-kamelets-utils
- camel:jackson
- camel:kamelet
- camel:core
47.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/mask-field-action.kamelet.yaml
48. Message Timestamp Router Action
Update the topic field as a function of the original topic name and the record’s timestamp field.
48.1. Configuration Options
The following table summarizes the configuration options available for the message-timestamp-router-action
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
timestampKeys * | Timestamp Keys | Comma separated list of Timestamp keys. The timestamp is taken from the first found field. |
| ||
timestampFormat | Timestamp Format | Format string for the timestamp that is compatible with java.text.SimpleDateFormat. | string |
| |
timestampKeyFormat | Timestamp Keys Format | Format of the timestamp keys. Possible values are 'timestamp' or any format string for the timestamp that is compatible with java.text.SimpleDateFormat. In case of 'timestamp' the field will be evaluated as milliseconds since 1970, so as a UNIX Timestamp. | string |
| |
topicFormat | Topic Format | Format string which can contain '$[topic]' and '$[timestamp]' as placeholders for the topic and timestamp, respectively. | string |
|
* = Fields marked with an asterisk are mandatory.
48.2. Dependencies
At runtime, the message-timestamp-router-action
Kamelet relies upon the presence of the following dependencies:
- mvn:org.apache.camel.kamelets:camel-kamelets-utils
- camel:jackson
- camel:kamelet
- camel:core
48.3. Kamelets source file
49. MongoDB Sink
Send documents to MongoDB.
This Kamelet expects a JSON as body.
Properties you can set as headers:
-
db-upsert
/ce-dbupsert
: if the database should create the element if it does not exist. Boolean value.
49.1. Configuration Options
The following table summarizes the configuration options available for the mongodb-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
collection * | MongoDB Collection | Sets the name of the MongoDB collection to bind to this endpoint. |
| ||
database * | MongoDB Database | Sets the name of the MongoDB database to target. |
| ||
hosts * | MongoDB Hosts | Comma separated list of MongoDB Host Addresses in host:port format. |
| ||
createCollection | Collection | Create collection during initialisation if it doesn’t exist. |
|
| |
password | MongoDB Password | User password for accessing MongoDB. |
| ||
username | MongoDB Username | Username for accessing MongoDB. |
| ||
writeConcern | Write Concern | Configure the level of acknowledgment requested from MongoDB for write operations, possible values are ACKNOWLEDGED, W1, W2, W3, UNACKNOWLEDGED, JOURNALED, MAJORITY. |
| ||
ssl | Enable Ssl for Mongodb Connection | whether to enable ssl connection to mongodb |
|
| |
sslValidationEnabled | Enables Ssl Certificates Validation and Host name checks. | IMPORTANT this should be disabled only in test environment since can pose security issues. |
|
|
* = Fields marked with an asterisk are mandatory.
49.2. Dependencies
At runtime, the mongodb-sink
Kamelet relies upon the presence of the following dependencies:
- camel:kamelet
- camel:mongodb
- camel:jackson
- camel:core
- mvn:org.apache.camel.kamelets:camel-kamelets-utils
49.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/mongodb-sink.kamelet.yaml
50. MongoDB Source
Consume documents from MongoDB.
If the persistentTailTracking option will be enabled, the consumer will keep track of the last consumed message and on the next restart, the consumption will restart from that message. In case of persistentTailTracking enabled, the tailTrackIncreasingField must be provided (by default it is optional).
If the persistentTailTracking option won’t be enabled, the consumer will consume the whole collection and wait in idle for new documents to consume.
50.1. Configuration Options
The following table summarizes the configuration options available for the mongodb-source
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
collection * | MongoDB Collection | Sets the name of the MongoDB collection to bind to this endpoint. |
| ||
database * | MongoDB Database | Sets the name of the MongoDB database to target. |
| ||
hosts * | MongoDB Hosts | Comma separated list of MongoDB Host Addresses in host:port format. |
| ||
password | MongoDB Password | User password for accessing MongoDB. |
| ||
username | MongoDB Username | Username for accessing MongoDB. The username must be present in the MongoDB’s authentication database (authenticationDatabase). By default, the MongoDB authenticationDatabase is 'admin'. |
| ||
persistentTailTracking | MongoDB Persistent Tail Tracking | Enable persistent tail tracking, which is a mechanism to keep track of the last consumed message across system restarts. The next time the system is up, the endpoint will recover the cursor from the point where it last stopped slurping records. |
|
| |
tailTrackIncreasingField | MongoDB Tail Track Increasing Field | Correlation field in the incoming record which is of increasing nature and will be used to position the tailing cursor every time it is generated. |
| ||
ssl | Enable Ssl for Mongodb Connection | whether to enable ssl connection to mongodb |
|
| |
sslValidationEnabled | Enable Ssl Certificates Validation and Host name checks | IMPORTANT this should be disabled only in test environment since can pose security issues. |
|
|
* = Fields marked with an asterisk are mandatory.
50.2. Dependencies
At runtime, the mongodb-source
Kamelet relies upon the presence of the following dependencies:
- camel:kamelet
- camel:mongodb
- camel:jackson
- mvn:org.apache.camel.kamelets:camel-kamelets-utils
50.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/mongodb-source.kamelet.yaml
51. MySQL Sink
Send data to a MySQL Database.
This Kamelet expects a JSON as body. The mapping between the JSON fields and parameters is done by key, so if you have the following query:
'INSERT INTO accounts (username,city) VALUES (:#username,:#city)'
The Kamelet needs to receive as input something like:
'{ "username":"oscerd", "city":"Rome"}'
51.1. Configuration Options
The following table summarizes the configuration options available for the mysql-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
databaseName * | Database Name | The Database Name we are pointing |
| ||
query * | Query | The Query to execute against the MySQL Database |
|
| |
serverName * | Server Name | Server Name for the data source |
|
| |
password | Password | The password to use for accessing a secured MySQL Database |
| ||
username | Username | The username to use for accessing a secured MySQL Database |
| ||
serverPort | Server Port | Server Port for the data source | string |
|
* = Fields marked with an asterisk are mandatory.
51.2. Dependencies
At runtime, the mysql-sink
Kamelet relies upon the presence of the following dependencies:
- camel:jackson
- camel:kamelet
- camel:sql
- mvn:org.apache.commons:commons-dbcp2:2.12.0.redhat-00001
51.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/mysql-sink.kamelet.yaml
52. PostgreSQL Sink
Send data to a PostgreSQL Database.
This Kamelet expects a JSON as body. The mapping between the JSON fields and parameters is done by key, so if you have the following query:
'INSERT INTO accounts (username,city) VALUES (:#username,:#city)'
The Kamelet needs to receive as input something like:
'{ "username":"oscerd", "city":"Rome"}'
52.1. Configuration Options
The following table summarizes the configuration options available for the postgresql-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
databaseName * | Database Name | The Database Name we are pointing |
| ||
query * | Query | The Query to execute against the PostgreSQL Database |
|
| |
serverName * | Server Name | Server Name for the data source |
|
| |
password | Password | The password to use for accessing a secured PostgreSQL Database |
| ||
username | Username | The username to use for accessing a secured PostgreSQL Database |
| ||
serverPort | Server Port | Server Port for the data source | string |
|
* = Fields marked with an asterisk are mandatory.
52.2. Dependencies
At runtime, the postgresql-sink
Kamelet relies upon the presence of the following dependencies:
- camel:jackson
- camel:kamelet
- camel:sql
- mvn:org.postgresql:postgresql
- mvn:org.apache.commons:commons-dbcp2:2.12.0.redhat-00001
52.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/postgresql-sink.kamelet.yaml
53. Predicate Filter Action
Filter based on a JsonPath Expression
53.1. Configuration Options
The following table summarizes the configuration options available for the predicate-filter-action
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
expression * | Expression | The JsonPath Expression to evaluate, without the external parenthesis. Since this is a filter, the expression will be a negation, this means that if the foo field of the example is equals to John, the message will go ahead, otherwise it will be filtered out. |
|
|
* = Fields marked with an asterisk are mandatory.
53.2. Dependencies
At runtime, the predicate-filter-action
Kamelet relies upon the presence of the following dependencies:
- camel:core
- camel:kamelet
- camel:jsonpath
53.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/predicate-filter-action.kamelet.yaml
54. Protobuf Deserialize Action
Deserialize payload to Protobuf
54.1. Configuration Options
The following table summarizes the configuration options available for the protobuf-deserialize-action
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
schema * | Schema | The Protobuf schema to use during serialization (as single-line) |
|
|
* = Fields marked with an asterisk are mandatory.
54.2. Dependencies
At runtime, the protobuf-deserialize-action
Kamelet relies upon the presence of the following dependencies:
- mvn:org.apache.camel.kamelets:camel-kamelets-utils
- camel:kamelet
- camel:core
- camel:jackson-protobuf
54.3. Kamelets source file
55. Protobuf Serialize Action
Serialize payload to Protobuf
55.1. Configuration Options
The following table summarizes the configuration options available for the protobuf-serialize-action
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
schema * | Schema | The Protobuf schema to use during serialization (as single-line) |
|
|
* = Fields marked with an asterisk are mandatory.
55.2. Dependencies
At runtime, the protobuf-serialize-action
Kamelet relies upon the presence of the following dependencies:
- mvn:org.apache.camel.kamelets:camel-kamelets-utils
- camel:kamelet
- camel:core
- camel:jackson-protobuf
55.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/protobuf-serialize-action.kamelet.yaml
56. Regex Router Action
Update the destination using the configured regular expression and replacement string
56.1. Configuration Options
The following table summarizes the configuration options available for the regex-router-action
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
regex * | Regex | Regular Expression for destination |
| ||
replacement * | Replacement | Replacement when matching |
|
* = Fields marked with an asterisk are mandatory.
56.2. Dependencies
At runtime, the regex-router-action
Kamelet relies upon the presence of the following dependencies:
- mvn:org.apache.camel.kamelets:camel-kamelets-utils
- camel:kamelet
- camel:core
56.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/regex-router-action.kamelet.yaml
57. Replace Field Action
Replace field with a different key in the message in transit.
- The required parameter 'renames' is a comma-separated list of colon-delimited renaming pairs like for example 'foo:bar,abc:xyz' and it represents the field rename mappings.
- The optional parameter 'enabled' represents the fields to include. If specified, only the named fields will be included in the resulting message.
- The optional parameter 'disabled' represents the fields to exclude. If specified, the listed fields will be excluded from the resulting message. This takes precedence over the 'enabled' parameter.
- The default value of 'enabled' parameter is 'all', so all the fields of the payload will be included.
- The default value of 'disabled' parameter is 'none', so no fields of the payload will be excluded.
57.1. Configuration Options
The following table summarizes the configuration options available for the replace-field-action
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
renames * | Renames | Comma separated list of field with new value to be renamed |
|
| |
disabled | Disabled | Comma separated list of fields to be disabled | string | "none" | |
enabled | Enabled | Comma separated list of fields to be enabled | string | "all" |
* = Fields marked with an asterisk are mandatory.
57.2. Dependencies
At runtime, the replace-field-action
Kamelet relies upon the presence of the following dependencies:
- mvn:org.apache.camel.kamelets:camel-kamelets-utils
- camel:core
- camel:jackson
- camel:kamelet
57.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/replace-field-action.kamelet.yaml
58. Salesforce Source
Receive updates from Salesforce.
58.1. Configuration Options
The following table summarizes the configuration options available for the salesforce-source
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
clientId * | Consumer Key | The Salesforce application consumer key |
| ||
clientSecret * | Consumer Secret | The Salesforce application consumer secret |
| ||
password * | Password | The Salesforce user password |
| ||
username * | Username | The Salesforce username |
| ||
query * | Query | The query to execute on Salesforce |
|
| |
topicName * | Topic Name | The name of the topic/channel to use |
|
| |
loginUrl | Login URL | The Salesforce instance login URL | string |
| |
query | Query | The query to execute on Salesforce. |
|
| |
topicName | Topic Name | The name of the topic or channel. |
|
| |
loginUrl | Login URL | The Salesforce instance login URL. |
| ||
notifyForFields | Notify For Fields | Notify for fields. |
|
|
|
clientId | Consumer Key | The Salesforce application consumer key. |
| ||
clientSecret | Consumer Secret | The Salesforce application consumer secret. |
| ||
userName | Username | The Salesforce username. |
| ||
password | Password | The Salesforce user password. |
| ||
notifyForOperationCreate | Notify Operation Create | Notify for create operation. |
|
| |
notifyForOperationUpdate | Notify Operation Update | Notify for update operation. |
|
| |
notifyForOperationDelete | Notify Operation Delete | Notify for delete operation. |
|
| |
notifyForOperationUndelete | Notify Operation Undelete | Notify for undelete operation. |
|
| |
operation | Operation | The operation to use |
|
| |
rawPayload | Raw Payload | Use raw payload String for request and response (either JSON or XML depending on format), instead of DTOs, false by default. |
|
| |
replayId | Replay Id | The replayId value to use when subscribing to the Streaming API. |
|
* = Fields marked with an asterisk are mandatory.
58.2. Dependencies
At runtime, the salesforce-source
Kamelet relies upon the presence of the following dependencies:
- camel:jackson
- camel:salesforce
- camel:kamelet
58.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/salesforce-source.kamelet.yaml
59. Salesforce Create Sink
Creates an object in Salesforce. The body of the message must contain the JSON of the salesforce object.
Example body: { "Phone": "555", "Name": "Antonia", "LastName": "Garcia" }
59.1. Configuration Options
The following table summarizes the configuration options available for the salesforce-create-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
clientId * | Consumer Key | The Salesforce application consumer key |
| ||
clientSecret * | Consumer Secret | The Salesforce application consumer secret |
| ||
password * | Password | The Salesforce user password |
| ||
username * | Username | The Salesforce username |
| ||
loginUrl | Login URL | The Salesforce instance login URL | string |
| |
sObjectName | Object Name | Type of the object |
|
|
* = Fields marked with an asterisk are mandatory.
59.2. Dependencies
At runtime, the salesforce-create-sink
Kamelet relies upon the presence of the following dependencies:
- camel:salesforce
- camel:kamelet
59.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/salesforce-create-sink.kamelet.yaml
60. Salesforce Delete Sink
Removes an object from Salesforce. The body received must be a JSON containing two keys: sObjectId and sObjectName.
Example body: { "sObjectId": "XXXXX0", "sObjectName": "Contact" }
60.1. Configuration Options
The following table summarizes the configuration options available for the salesforce-delete-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
clientId * | Consumer Key | The Salesforce application consumer key |
| ||
clientSecret * | Consumer Secret | The Salesforce application consumer secret |
| ||
password * | Password | The Salesforce user password |
| ||
username * | Username | The Salesforce username |
| ||
loginUrl | Login URL | The Salesforce instance login URL | string |
|
* = Fields marked with an asterisk are mandatory.
60.2. Dependencies
At runtime, the salesforce-delete-sink
Kamelet relies upon the presence of the following dependencies:
- camel:salesforce
- camel:kamelet
- camel:core
- camel:jsonpath
60.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/salesforce-delete-sink.kamelet.yaml
61. Salesforce Update Sink
Update an object in Salesforce.
The body received must contain a JSON key-value pair for each property to update inside the payload attribute, for example:
{ "payload": { "Phone": "1234567890", "Name": "Antonia" } }
The body received must include the sObjectName
and sObjectId
properties, for example:
{ "payload": { "Phone": "1234567890", "Name": "Antonia" }, "sObjectId": "sObjectId", "sObjectName": "sObjectName" }
61.1. Configuration Options
The following table summarizes the configuration options available for the salesforce-update-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
clientId * | Consumer Key | The Salesforce application consumer key |
| ||
clientSecret * | Consumer Secret | The Salesforce application consumer secret |
| ||
password * | Password | The Salesforce user password |
| ||
username * | Username | The Salesforce username |
| ||
loginUrl | Login URL | The Salesforce instance login URL | string |
|
* = Fields marked with an asterisk are mandatory.
61.2. Dependencies
At runtime, the salesforce-update-sink
Kamelet relies upon the presence of the following dependencies:
- camel:core
- camel:jackson
- camel:jsonpath
- camel:kamelet
- camel:salesforce
61.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/salesforce-update-sink.kamelet.yaml
62. SFTP Sink
Send data to an SFTP Server.
The Kamelet expects the following headers to be set:
-
file
/ce-file
: as the file name to upload
If the header won’t be set the exchange ID will be used as file name.
62.1. Configuration Options
The following table summarizes the configuration options available for the sftp-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
connectionHost * | Connection Host | The hostname of the SFTP server |
| ||
connectionPort * | Connection Port | The port of the SFTP server |
|
| |
directoryName * | Directory Name | The starting directory |
| ||
username | Username | The username to access the FTP server. |
| ||
password | Password | The password to access the FTP server. |
| ||
passiveMode | Passive Mode | Specifies to use passive mode connection. |
|
| |
fileExist | File Existence | How to behave in case of file already existent. |
|
|
|
binary | Binary | Specifies the file transfer mode, BINARY or ASCII. Default is ASCII (false). |
|
| |
privateKeyFile | Private Key File | Set the private key file so that the SFTP endpoint can do private key verification. |
| ||
privateKeyPassphrase | Private Key Passphrase | Set the private key file passphrase so that the SFTP endpoint can do private key verification. |
| ||
privateKeyUri | Private Key URI | Set the private key file (loaded from classpath by default) so that the SFTP endpoint can do private key verification. |
| ||
strictHostKeyChecking | Strict Host Checking | Sets whether to use strict host key checking. |
|
| |
useUserKnownHostsFile | Use User Known Hosts File | If knownHostFile has not been explicit configured then use the host file from System.getProperty(user.home)/.ssh/known_hosts. |
|
| |
autoCreate | Autocreate Missing Directories | Automatically create the directory the files should be written to. |
|
|
* = Fields marked with an asterisk are mandatory.
62.2. Dependencies
At runtime, the sftp-sink
Kamelet relies upon the presence of the following dependencies:
- camel:ftp
- camel:core
- camel:kamelet
62.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/sftp-sink.kamelet.yaml
63. SFTP Source
Receive data from an SFTP Server.
63.1. Configuration Options
The following table summarizes the configuration options available for the sftp-source
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
connectionHost * | Connection Host | The hostname of the SFTP server. |
| ||
connectionPort * | Connection Port | The port of the SFTP server. |
|
| |
directoryName * | Directory Name | The starting directory |
| ||
username | Username | The username to access the SFTP server. |
| ||
password | Password | The password to access the SFTP server. |
| ||
passiveMode | Passive Mode | Sets the passive mode connection. |
|
| |
recursive | Recursive | If a directory, look for files in all subdirectories as well. |
|
| |
idempotent | Idempotency | Skip already-processed files. |
|
| |
ignoreFileNotFoundOrPermissionError | Ignore File Not Found Or Permission Error | Whether to ignore when (trying to list files in directories or when downloading a file), which does not exist or due to permission error. By default when a directory or file does not exists or insufficient permission, then an exception is thrown. Setting this option to true allows to ignore that instead. |
|
| |
binary | Binary | Specifies the file transfer mode, BINARY or ASCII. Default is ASCII (false). |
|
| |
privateKeyFile | Private Key File | Set the private key file so that the SFTP endpoint can do private key verification. |
| ||
privateKeyPassphrase | Private Key Passphrase | Set the private key file passphrase so that the SFTP endpoint can do private key verification. |
| ||
privateKeyUri | Private Key URI | Set the private key file (loaded from classpath by default) so that the SFTP endpoint can do private key verification. |
| ||
strictHostKeyChecking | Strict Host Checking | Sets whether to use strict host key checking. |
|
| |
useUserKnownHostsFile | Use User Known Hosts File | If knownHostFile has not been explicit configured then use the host file from System.getProperty(user.home)/.ssh/known_hosts. |
|
| |
autoCreate | Autocreate Missing Directories | Automatically create starting directory. |
|
| |
delete | Delete | If true, the file will be deleted after it is processed successfully. |
|
|
* = Fields marked with an asterisk are mandatory.
63.2. Dependencies
At runtime, the sftp-source
Kamelet relies upon the presence of the following dependencies:
- camel:ftp
- camel:core
- camel:kamelet
63.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/sftp-source.kamelet.yaml
64. Simple Filter Action
Filter based on simple expression
64.1. Configuration Options
The following table summarizes the configuration options available for the simple-filter-action
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
expression | Simple Expression | Required A simple expression to apply on the exchange to filter out some exchange. | string |
64.2. Dependencies
At runtime, the simple-filter-action
Kamelet relies on the presence of the following dependencies:
- camel:core
- camel:kamelet
64.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/simple-filter-action.kamelet.yaml
65. Slack Source
Receive messages from a Slack channel.
65.1. Configuration Options
The following table summarizes the configuration options available for the slack-source
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
channel * | Channel | The Slack channel to receive messages from. |
| "#myroom" | |
token * | Token |
"The Bot User OAuth Access Token to access Slack. A Slack app that has the following permissions is required: |
|
| |
serverUrl | Server URL | The Slack API server endpoint URL. |
|
|
|
delay | Delay | The delay between polls. If no unit provided, milliseconds is the default. |
|
|
|
naturalOrder | Natural Order | Create exchanges in natural order (oldest to newest) or not. |
|
|
* = Fields marked with an asterisk are mandatory.
65.2. Dependencies
At runtime, the slack-source
Kamelet relies upon the presence of the following dependencies:
- camel:kamelet
- camel:slack
- camel:gson
65.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/slack-source.kamelet.yaml
66. Microsoft SQL Server Sink
Send data to a Microsoft SQL Server Database.
This Kamelet expects a JSON as body. The mapping between the JSON fields and parameters is done by key, so if you have the following query:
'INSERT INTO accounts (username,city) VALUES (:#username,:#city)'
The Kamelet needs to receive as input something like:
'{ "username":"oscerd", "city":"Rome"}'
66.1. Configuration Options
The following table summarizes the configuration options available for the sqlserver-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
serverName * | Server Name | The server name for the data source. | string | localhost | |
username * | Username | The username to access a secured SQL Server Database. | string | ||
password * | Password | The password to access a secured SQL Server Database. | string | password | |
query * | Query | The query to execute against the SQL Server Database. | string | 'INSERT INTO accounts (username,city) VALUES (:#username,:#city)' | |
databaseName * | Database Name | The name of the SQL Server Database. | string | ||
serverPort | Server Port | The server port for the data source. | string | 1433 | |
encrypt | Encrypt Connection | Encrypt the connection to SQL Server. | boolean | false | |
trustServerCertificate | Trust Server Certificate | Trust Server Certificate | boolean | true |
* = Fields marked with an asterisk are mandatory.
66.2. Dependencies
At runtime, the sqlserver-sink
Kamelet relies upon the presence of the following dependencies:
- camel:jackson
- camel:kamelet
- camel:sql
- mvn:org.apache.commons:commons-dbcp2:2.12.0.redhat-00001
66.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/sqlserver-sink.kamelet.yaml
67. Telegram Source
Receive all messages that people send to your Telegram bot.
To create a bot, contact the @botfather account using the Telegram app.
The source attaches the following headers to the messages:
-
chat-id
/ce-chatid
: the ID of the chat where the message comes from
67.1. Configuration Options
The following table summarizes the configuration options available for the telegram-source
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
authorizationToken * | Token | The token to access your bot on Telegram. You you can obtain it from the Telegram @botfather. |
|
* = Fields marked with an asterisk are mandatory.
67.2. Dependencies
At runtime, the telegram-source
Kamelet relies upon the presence of the following dependencies:
- camel:jackson
- camel:kamelet
- camel:telegram
- camel:core
67.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/telegram-source.kamelet.yaml
68. Throttle Action
The Throttle action allows you to ensure that a specific sink does not get overloaded.
68.1. Configuration Options
The following table summarizes the configuration options available for the throttle-action
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
messages * | Messages Number | The number of messages to send in the time period set | integer |
| |
timePeriod | Time Period | Sets the time period during which the maximum request count is valid for, in milliseconds | string |
|
* = Fields marked with an asterisk are mandatory.
68.2. Dependencies
At runtime, the throttle-action
Kamelet relies upon the presence of the following dependencies:
- camel:core
- camel:kamelet
68.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/throttle-action.kamelet.yaml
69. Timer Source
Produces periodic events with a custom payload.
69.1. Configuration Options
The following table summarizes the configuration options available for the timer-source
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
message * | Message | The message to generate |
|
| |
contentType | Content Type | The content type of the message being generated | string |
| |
period | Period | The interval between two events in milliseconds | integer |
| |
repeatCount | Repeat Count | Specifies the maximum limit of the number of fires | integer |
* = Fields marked with an asterisk are mandatory.
69.2. Dependencies
At runtime, the timer-source
Kamelet relies upon the presence of the following dependencies:
- camel:core
- camel:timer
- camel:kamelet
69.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/timer-source.kamelet.yaml
70. Timestamp Router Action
Update the topic field as a function of the original topic name and the record timestamp.
70.1. Configuration Options
The following table summarizes the configuration options available for the timestamp-router-action
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
timestampFormat | Timestamp Format | Format string for the timestamp that is compatible with java.text.SimpleDateFormat. | string |
| |
timestampHeaderName | Timestamp Header Name | The name of the header containing a timestamp | string |
| |
topicFormat | Topic Format | Format string which can contain '$[topic]' and '$[timestamp]' as placeholders for the topic and timestamp, respectively. | string |
|
* = Fields marked with an asterisk are mandatory.
70.2. Dependencies
At runtime, the timestamp-router-action
Kamelet relies upon the presence of the following dependencies:
- mvn:org.apache.camel.kamelets:camel-kamelets-utils
- camel:kamelet
- camel:core
70.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/timestamp-router-action.kamelet.yaml
71. Value to Key Action
Replace the Kafka record key with a new key formed from a subset of fields in the body
71.1. Configuration Options
The following table summarizes the configuration options available for the value-to-key-action
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
fields * | Fields | Comma separated list of fields to be used to form the new key |
|
* = Fields marked with an asterisk are mandatory.
71.2. Dependencies
At runtime, the value-to-key-action
Kamelet relies upon the presence of the following dependencies:
- mvn:org.apache.camel.kamelets:camel-kamelets-utils
- camel:core
- camel:jackson
- camel:kamelet
71.3. Kamelets source file
https://github.com/apache/camel-kamelets/blob/4.8.x/kamelets/value-to-key-action.kamelet.yaml