이 콘텐츠는 선택한 언어로 제공되지 않습니다.
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.
Chapter 1. AWS DynamoDB Sink 링크 복사링크가 클립보드에 복사되었습니다!
Send data to Amazon DynamoDB. The sent data inserts, updates, or deletes an item on the specified AWS DynamoDB table.
1.1. Authentication methods 링크 복사링크가 클립보드에 복사되었습니다!
In this Kamelet you can avoid using explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
The order of evaluation for Default Credentials Provider is the following:
-
Java system properties -
aws.accessKeyIdandaws.secretKey. -
Environment variables -
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY. - Web Identity Token from AWS STS.
- The shared credentials and config files.
-
Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable
AWS_CONTAINER_CREDENTIALS_RELATIVE_URIis set. - Amazon EC2 Instance profile credentials.
You can also use the Profile Credentials Provider, by setting the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
Only one of access key/secret key or default credentials provider could be used
For more information, see the AWS credentials documentation
1.2. Expected Data format for sink 링크 복사링크가 클립보드에 복사되었습니다!
This Kamelet expects a JSON-formatted body and it must include the primary key values that define the DynamoDB item. The mapping between the JSON fields and table attribute values is done by key. For example, for '{"username":"oscerd", "city":"Rome"}' input, the Kamelet inserts or update an item in the specified AWS DynamoDB table and sets the values for the 'username' and 'city' attributes.
For PutItem operation the Json body defines all item attributes. For DeleteItem operation the Json body defines only the primary key attributes that identify the item to delete. For UpdateItem operation the Json body defines both key attributes to identify the item to be updated and all item attributes tht get updated on the item.
The given JSON body can use operation, key and item as top level properties that are mapped to the respective attribute value maps.
{
"operation": "PutItem"
"key": {},
"item": {}
}
{
"operation": "PutItem"
"key": {},
"item": {}
}
1.3. 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 access. | string | ||
| table * | Table | The name of the DynamoDB table. | string | ||
| accessKey | Access Key | The access key obtained from AWS. | string | ||
| operation | Operation | The operation to perform. | string | PutItem | PutItem |
| overrideEndpoint | Endpoint Overwrite |
Select this option to override the endpoint URI. To use this option, you must also provide a URI for the | boolean | False | |
| profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter sets the profile name. | string | ||
| secretKey | Secret Key | The secret key obtained from AWS. | string | ||
| sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. | string | ||
| uriEndpointOverride | Overwrite Endpoint URI |
The overriding endpoint URI. To use this option, you must also select the | string | ||
| useDefaultCredentialsProvider | Default Credentials Provider | If true, the DynamoDB client loads credentials through a default credentials provider. If false, it uses the basic authentication method (access key and secret key). | boolean | False | |
| useProfileCredentialsProvider | Profile Credentials Provider | Set whether the DynamoDB client should expect to load credentials through a profile credentials provider. | boolean | False | |
| 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. | boolean | False |
* = Fields marked with an asterisk are mandatory.
1.4. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
1.4.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
1.5. Usage 링크 복사링크가 클립보드에 복사되었습니다!
1.5.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
1.5.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
1.5.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
1.5.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-ddb-sink Kamelet as a Knative sink by binding it to a Knative object.
aws-ddb-sink-binding.yaml
1.5.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-ddb-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
aws-ddb-sink-binding.yaml
1.6. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 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) | string | {"type": "record", "namespace": "com.example", "name": "FullName", "fields": [{"name": "first", "type": "string"},{"name": "last", "type": "string"}]} | |
| validate | Validate | Indicates if the content must be validated against the schema | boolean | True |
* = Fields marked with an asterisk are mandatory.
2.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
2.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
2.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
2.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
2.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
2.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
2.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the avro-deserialize-action Kamelet as an intermediate step in a Knative binding.
avro-deserialize-action-binding.yaml
2.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the avro-deserialize-action Kamelet as an intermediate step in a Kafka binding.
avro-deserialize-action-binding.yaml
2.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 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) | string | {"type": "record", "namespace": "com.example", "name": "FullName", "fields": [{"name": "first", "type": "string"},{"name": "last", "type": "string"}]} | |
| validate | Validate | Indicates if the content must be validated against the schema | boolean | True |
* = Fields marked with an asterisk are mandatory.
3.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
3.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
3.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
3.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
3.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
3.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
3.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the avro-serialize-action Kamelet as an intermediate step in a Knative binding.
avro-serialize-action-binding.yaml
3.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the avro-serialize-action Kamelet as an intermediate step in a Kafka binding.
avro-serialize-action-binding.yaml
3.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 4. AWS CloudWatch Metrics Sink 링크 복사링크가 클립보드에 복사되었습니다!
Send data to Amazon CloudWatch metrics.
4.1. Authentication methods 링크 복사링크가 클립보드에 복사되었습니다!
In this Kamelet you can avoid using explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
The order of evaluation for Default Credentials Provider is the following:
-
Java system properties -
aws.accessKeyIdandaws.secretKey. -
Environment variables -
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY. - Web Identity Token from AWS STS.
- The shared credentials and config files.
-
Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable
AWS_CONTAINER_CREDENTIALS_RELATIVE_URIis set. - Amazon EC2 Instance profile credentials.
You can also use the Profile Credentials Provider, by setting the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
Only one of access key/secret key or default credentials provider could be used
For more information, see the AWS credentials documentation
4.2. Metric Headers 링크 복사링크가 클립보드에 복사되었습니다!
In this Kamelet you could use the following headers for metrics:
-
metric-name/ce-metricnamefor the metric name. -
metric-value/ce-metricvaluefor the metric value. -
metric-unit/ce-metricunitfor the metric unit. -
metric-timestamp/ce-metrictimestampfor the metric timestamp. -
metric-dimension-name/ce-metricdimensionnamefor the dimension name. -
metric-dimension-value/ce-metricdimensionvaluefor the dimension value.
4.3. Configuration Options 링크 복사링크가 클립보드에 복사되었습니다!
The following table summarizes the configuration options available for the aws-cloudwatch-sink Kamelet:
| Property | Name | Description | Type | Default | Example |
|---|---|---|---|---|---|
| cwNamespace * | Cloud Watch Namespace | The CloudWatch metric namespace. | string | ||
| region * | AWS Region | The AWS region to access. | string | ||
| accessKey | Access Key | The access key obtained from AWS. | 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 | False | |
| profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter sets the profile name. | string | ||
| secretKey | Secret Key | The secret key obtained from AWS. | string | ||
| sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. | string | ||
| uriEndpointOverride | Overwrite Endpoint URI |
The overriding endpoint URI. To use this option, you must also select the | string | ||
| useDefaultCredentialsProvider | Default Credentials Provider | If true, the Cloudwatch client loads credentials through a default credentials provider. If false, it uses the basic authentication method (access key and secret key). | boolean | False | |
| useProfileCredentialsProvider | Profile Credentials Provider | Set whether the Cloudwatch client should expect to load credentials through a profile credentials provider. | boolean | False | |
| useSessionCredentials | Session Credentials | Set whether the Cloudwatch 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 Cloudwatch. | boolean | False |
* = Fields marked with an asterisk are mandatory.
4.4. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
4.4.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
4.5. Usage 링크 복사링크가 클립보드에 복사되었습니다!
4.5.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
4.5.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
4.5.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
4.5.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-cloudwatch-sink Kamelet as a Knative sink by binding it to a Knative object.
aws-cloudwatch-sink-binding.yaml
4.5.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-cloudwatch-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
aws-cloudwatch-sink-binding.yaml
4.6. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 5. AWS DynamoDB Streams Source 링크 복사링크가 클립보드에 복사되었습니다!
Receive events from Amazon DynamoDB Streams.
5.1. Authentication methods 링크 복사링크가 클립보드에 복사되었습니다!
In this Kamelet you can avoid using explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
The order of evaluation for Default Credentials Provider is the following:
-
Java system properties -
aws.accessKeyIdandaws.secretKey. -
Environment variables -
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY. - Web Identity Token from AWS STS.
- The shared credentials and config files.
-
Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable
AWS_CONTAINER_CREDENTIALS_RELATIVE_URIis set. - Amazon EC2 Instance profile credentials.
You can also use the Profile Credentials Provider, by setting the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
Only one of access key/secret key or default credentials provider could be used
For more information, see the AWS credentials documentation
5.2. Configuration Options 링크 복사링크가 클립보드에 복사되었습니다!
The following table summarizes the configuration options available for the aws-ddb-streams-source Kamelet:
| Property | Name | Description | Type | Default | Example |
|---|---|---|---|---|---|
| region * | AWS Region | The AWS region to access. | string | ||
| table * | Table | The name of the DynamoDB table. | string | ||
| accessKey | Access Key | The access key obtained from AWS. | string | ||
| delay | Delay | The number of milliseconds before the next poll from the database. | integer | 500 | |
| overrideEndpoint | Endpoint Overwrite |
Select this option to override the endpoint URI. To use this option, you must also provide a URI for the | boolean | False | |
| profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter sets the profile name. | string | ||
| secretKey | Secret Key | The secret key obtained from AWS. | string | ||
| sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. | string | ||
| streamIteratorType | Stream Iterator Type | Defines where in the DynamoDB stream to start getting records. There are two enums and the value can be one of FROM_LATEST and FROM_START. Note that using FROM_START can cause a significant delay before the stream has caught up to real-time. | string | FROM_LATEST | |
| uriEndpointOverride | Overwrite Endpoint URI |
The overriding endpoint URI. To use this option, you must also select the | string | ||
| useDefaultCredentialsProvider | Default Credentials Provider |
If | boolean | False | |
| useProfileCredentialsProvider | Profile Credentials Provider | Set whether the DynamoDB client should expect to load credentials through a profile credentials provider. | boolean | False | |
| 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. | boolean | False |
* = Fields marked with an asterisk are mandatory.
5.3. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
5.3.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
5.4. Usage 링크 복사링크가 클립보드에 복사되었습니다!
5.4.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
5.4.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
5.4.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
5.4.2. Knative Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-ddb-streams-source Kamelet as a Knative source by binding it to a Knative object.
aws-ddb-streams-source-binding.yaml
5.4.3. Kafka Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-ddb-streams-source Kamelet as a Kafka source by binding it to a Kafka topic.
aws-ddb-streams-source-binding.yaml
5.5. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 6. AWS Kinesis Firehose Sink 링크 복사링크가 클립보드에 복사되었습니다!
Send message to an AWS Kinesis Firehose Stream.
6.1. Authentication methods 링크 복사링크가 클립보드에 복사되었습니다!
In this Kamelet you can avoid using explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
The order of evaluation for Default Credentials Provider is the following:
-
Java system properties -
aws.accessKeyIdandaws.secretKey. -
Environment variables -
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY. - Web Identity Token from AWS STS.
- The shared credentials and config files.
-
Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable
AWS_CONTAINER_CREDENTIALS_RELATIVE_URIis set. - Amazon EC2 Instance profile credentials.
You can also use the Profile Credentials Provider, by setting the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
Only one of access key/secret key or default credentials provider could be used
For more information, see the AWS credentials documentation
6.2. Configuration Options 링크 복사링크가 클립보드에 복사되었습니다!
The following table summarizes the configuration options available for the aws-kinesis-firehose-sink Kamelet:
| Property | Name | Description | Type | Default | Example |
|---|---|---|---|---|---|
| region * | AWS Region | The AWS region to access. | string | ||
| streamName * | Stream Name | The name of the stream we want to send to data to. | string | ||
| accessKey | Access Key | The access key obtained from AWS. | 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 | False | |
| profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter sets the profile name. | string | ||
| secretKey | Secret Key | The secret key obtained from AWS. | string | ||
| sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. | string | ||
| uriEndpointOverride | Overwrite Endpoint URI |
The overriding endpoint URI. To use this option, you must also select the | string | ||
| useDefaultCredentialsProvider | Default Credentials Provider | Set whether the Kinesis Firehose client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | boolean | False | |
| useProfileCredentialsProvider | Profile Credentials Provider | Set whether the Kinesis Firehose client should expect to load credentials through a profile credentials provider. | boolean | False | |
| useSessionCredentials | Session Credentials | Set whether the Kinesis Firehose 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 Firehose. | boolean | False |
* = Fields marked with an asterisk are mandatory.
6.3. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
6.3.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
6.4. Usage 링크 복사링크가 클립보드에 복사되었습니다!
6.4.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
6.4.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
6.4.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
6.4.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-kinesis-firehose-sink Kamelet as a Knative sink by binding it to a Knative object.
aws-kinesis-firehose-sink-binding.yaml
6.4.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-kinesis-firehose-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
aws-kinesis-firehose-sink-binding.yaml
6.5. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 7. AWS Kinesis Sink 링크 복사링크가 클립보드에 복사되었습니다!
Send data to AWS Kinesis.
7.1. Authentication methods 링크 복사링크가 클립보드에 복사되었습니다!
In this Kamelet you can avoid using explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
The order of evaluation for Default Credentials Provider is the following:
-
Java system properties -
aws.accessKeyIdandaws.secretKey. -
Environment variables -
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY. - Web Identity Token from AWS STS.
- The shared credentials and config files.
-
Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable
AWS_CONTAINER_CREDENTIALS_RELATIVE_URIis set. - Amazon EC2 Instance profile credentials.
You can also use the Profile Credentials Provider, by setting the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
Only one of access key/secret key or default credentials provider could be used
For more information, see the AWS credentials documentation
7.2. Optional Headers 링크 복사링크가 클립보드에 복사되었습니다!
In the header, you can optionally set the file / ce-partition property to set the Kinesis partition key.
If you do not set the property in the header, the Kamelet uses the exchange ID for the partition key.
You can also set the sequence-number / ce-sequencenumber property in the header to specify the Sequence number.
7.3. 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 access. | string | ||
| stream * | Stream Name | The Kinesis stream that you want to access. The Kinesis stream that you specify must already exist. | string | ||
| accessKey | Access Key | The access key obtained from AWS. | 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 | False | |
| profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter sets the profile name. | string | ||
| secretKey | Secret Key | The secret key obtained from AWS. | string | ||
| sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. | string | ||
| uriEndpointOverride | Overwrite Endpoint URI |
The overriding endpoint URI. To use this option, you must also select the | string | ||
| 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). | boolean | False | |
| useProfileCredentialsProvider | Profile Credentials Provider | Set whether the Kinesis client should expect to load credentials through a profile credentials provider. | boolean | False | |
| 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. | boolean | False |
* = Fields marked with an asterisk are mandatory.
7.4. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
7.4.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
7.5. Usage 링크 복사링크가 클립보드에 복사되었습니다!
7.5.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
7.5.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
7.5.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
7.5.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-kinesis-sink Kamelet as a Knative sink by binding it to a Knative object.
aws-kinesis-sink-binding.yaml
7.5.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-kinesis-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
aws-kinesis-sink-binding.yaml
7.6. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 8. AWS Kinesis Source 링크 복사링크가 클립보드에 복사되었습니다!
Receive data from AWS Kinesis.
8.1. Authentication methods 링크 복사링크가 클립보드에 복사되었습니다!
In this Kamelet you can avoid using explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
The order of evaluation for Default Credentials Provider is the following:
-
Java system properties -
aws.accessKeyIdandaws.secretKey. -
Environment variables -
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY. - Web Identity Token from AWS STS.
- The shared credentials and config files.
-
Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable
AWS_CONTAINER_CREDENTIALS_RELATIVE_URIis set. - Amazon EC2 Instance profile credentials.
You can also use the Profile Credentials Provider, by setting the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
Only one of access key/secret key or default credentials provider could be used
For more information, see the AWS credentials documentation
8.2. Usage example with plain consumer 링크 복사링크가 클립보드에 복사되었습니다!
You could consume the stream content directly
8.3. Usage example with KCL Consumer 링크 복사링크가 클립보드에 복사되었습니다!
You could consume the stream content with the KCL support
With the useKclConsumers enabled, you won’t have to deal with shard iteration directly. Everything is managed by the AWS Kinesis client library and the KCL layer.
As a side note you need to remember that the KCL consumer will need access to DynamoDB and Cloudwatch services from AWS, so it will create clients to these services under the hood and it will use them.
8.4. 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 access. | string | ||
| stream * | Stream Name | The Kinesis stream that you want to access. The Kinesis stream that you specify must already exist. | string | ||
| accessKey | Access Key | The access key obtained from AWS. | string | ||
| asyncClient | Async Client | If we want a KinesisAsyncClient instance set it to true. | boolean | False | |
| delay | Delay | The number of milliseconds before the next poll of the selected stream. | integer | 500 | |
| kclDisableCloudwatchMetricsExport | KCL Disable Cloudwatch Metrics Export | Define if we want to use a KCL Consumer and disable the CloudWatch Metrics Export | boolean | False | |
| overrideEndpoint | Endpoint Overwrite |
Select this option to override the endpoint URI. To use this option, you must also provide a URI for the | boolean | False | |
| profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter sets the profile name. | string | ||
| secretKey | Secret Key | The secret key obtained from AWS. | string | ||
| sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. | string | ||
| uriEndpointOverride | Overwrite Endpoint URI |
The overriding endpoint URI. To use this option, you must also select the | string | ||
| 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). | boolean | False | |
| useKclConsumers | KCL Consumer | If we want to a KCL Consumer set it to true | boolean | False | |
| useProfileCredentialsProvider | Profile Credentials Provider | Set whether the Kinesis client should expect to load credentials through a profile credentials provider. | boolean | False | |
| 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. | boolean | False |
* = Fields marked with an asterisk are mandatory.
8.5. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
8.5.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
8.6. Usage 링크 복사링크가 클립보드에 복사되었습니다!
8.6.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
8.6.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
8.6.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
8.6.2. Knative Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-kinesis-source Kamelet as a Knative source by binding it to a Knative object.
aws-kinesis-source-binding.yaml
8.6.3. Kafka Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-kinesis-source Kamelet as a Kafka source by binding it to a Kafka topic.
aws-kinesis-source-binding.yaml
8.7. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 9. AWS Lambda Sink 링크 복사링크가 클립보드에 복사되었습니다!
Send a payload to an AWS Lambda function.
9.1. Authentication methods 링크 복사링크가 클립보드에 복사되었습니다!
In this Kamelet you can avoid using explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
The order of evaluation for Default Credentials Provider is the following:
-
Java system properties -
aws.accessKeyIdandaws.secretKey. -
Environment variables -
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY. - Web Identity Token from AWS STS.
- The shared credentials and config files.
-
Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable
AWS_CONTAINER_CREDENTIALS_RELATIVE_URIis set. - Amazon EC2 Instance profile credentials.
You can also use the Profile Credentials Provider, by setting the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
Only one of access key/secret key or default credentials provider could be used
For more information, see the AWS credentials documentation
9.2. 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. | string | ||
| region * | AWS Region | The AWS region to access. | string | ||
| accessKey | Access Key | The access key obtained from AWS. | string | ||
| profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter sets the profile name. | string | ||
| secretKey | Secret Key | The secret key obtained from AWS. | string | ||
| sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. | string | ||
| 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). | boolean | False | |
| useProfileCredentialsProvider | Profile Credentials Provider | Set whether the Lambda client should expect to load credentials through a profile credentials provider. | boolean | False | |
| 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. | boolean | False |
* = Fields marked with an asterisk are mandatory.
9.3. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
9.3.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
9.4. Usage 링크 복사링크가 클립보드에 복사되었습니다!
9.4.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
9.4.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
9.4.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
9.4.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-lambda-sink Kamelet as a Knative sink by binding it to a Knative object.
aws-lambda-sink-binding.yaml
9.4.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-lambda-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
aws-lambda-sink-binding.yaml
9.5. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 10. AWS Redshift Sink 링크 복사링크가 클립보드에 복사되었습니다!
Send data to an AWS Redshift Database.
10.1. Authentication methods 링크 복사링크가 클립보드에 복사되었습니다!
In this Kamelet you can avoid using explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
The order of evaluation for Default Credentials Provider is the following:
-
Java system properties -
aws.accessKeyIdandaws.secretKey. -
Environment variables -
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY. - Web Identity Token from AWS STS.
- The shared credentials and config files.
-
Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable
AWS_CONTAINER_CREDENTIALS_RELATIVE_URIis set. - Amazon EC2 Instance profile credentials.
You can also use the Profile Credentials Provider, by setting the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
Only one of access key/secret key or default credentials provider could be used
For more information, see the AWS credentials documentation
10.2. Expected Data format for sink 링크 복사링크가 클립보드에 복사되었습니다!
The Kamelet expects a JSON-formatted body. Use key:value pairs to map the JSON fields and parameters. For example, here is a query:
'INSERT INTO accounts (username,city) VALUES (:#username,:#city)'
'INSERT INTO accounts (username,city) VALUES (:#username,:#city)'
Here is example input for the example query:
'{ "username":"oscerd", "city":"Rome"}'
'{ "username":"oscerd", "city":"Rome"}'
10.3. 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 name of the AWS RedShift Database. | string | ||
| password * | Password | The password to access a secured AWS Redshift Database. | string | ||
| query * | Query | The query to execute against the AWS Redshift Database. | string | INSERT INTO accounts (username,city) VALUES (:#username,:#city) | |
| serverName * | Server Name | The server name for the data source. | string | localhost | |
| username * | Username | The username to access a secured AWS Redshift Database. | string | ||
| serverPort | Server Port | The server port for the AWS RedShi data source. | string | 5439 |
* = Fields marked with an asterisk are mandatory.
10.4. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
10.4.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
10.5. Usage 링크 복사링크가 클립보드에 복사되었습니다!
10.5.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
10.5.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
10.5.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
10.5.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-redshift-sink Kamelet as a Knative sink by binding it to a Knative object.
aws-redshift-sink-binding.yaml
10.5.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-redshift-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
aws-redshift-sink-binding.yaml
10.6. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 11. AWS SNS Sink 링크 복사링크가 클립보드에 복사되었습니다!
Send message to an Amazon Simple Notification Service (SNS) topic.
11.1. Authentication methods 링크 복사링크가 클립보드에 복사되었습니다!
In this Kamelet you can avoid using explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
The order of evaluation for Default Credentials Provider is the following:
-
Java system properties -
aws.accessKeyIdandaws.secretKey. -
Environment variables -
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY. - Web Identity Token from AWS STS.
- The shared credentials and config files.
-
Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable
AWS_CONTAINER_CREDENTIALS_RELATIVE_URIis set. - Amazon EC2 Instance profile credentials.
You can also use the Profile Credentials Provider, by setting the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
Only one of access key/secret key or default credentials provider could be used
For more information, see the AWS credentials documentation
11.2. Optional Headers 링크 복사링크가 클립보드에 복사되었습니다!
In the Kamelet you can optionally set the following header:
-
subject/ce-subject: the subject of the message
11.3. 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 access. | string | ||
| topicNameOrArn * | Topic Name | The SNS topic name name or Amazon Resource Name (ARN). | string | ||
| accessKey | Access Key | The access key obtained from AWS. | string | ||
| autoCreateTopic | Autocreate Topic | Setting the autocreation of the SNS topic. | boolean | False | |
| overrideEndpoint | Endpoint Overwrite |
Select this option to override the endpoint URI. To use this option, you must also provide a URI for the | boolean | False | |
| profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter sets the profile name. | string | ||
| secretKey | Secret Key | The secret key obtained from AWS. | string | ||
| sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. | string | ||
| uriEndpointOverride | Overwrite Endpoint URI |
The overriding endpoint URI. To use this option, you must also select the | string | ||
| 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). | boolean | False | |
| useProfileCredentialsProvider | Profile Credentials Provider | Set whether the SNS client should expect to load credentials through a profile credentials provider. | boolean | False | |
| 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. | boolean | False |
* = Fields marked with an asterisk are mandatory.
11.4. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
11.4.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
11.5. Usage 링크 복사링크가 클립보드에 복사되었습니다!
11.5.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
11.5.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
11.5.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
11.5.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-sns-sink Kamelet as a Knative sink by binding it to a Knative object.
aws-sns-sink-binding.yaml
11.5.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-sns-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
aws-sns-sink-binding.yaml
11.6. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 12. AWS SQS Sink 링크 복사링크가 클립보드에 복사되었습니다!
Send messages to an Amazon Simple Queue Service (SQS) queue.
12.1. Authentication methods 링크 복사링크가 클립보드에 복사되었습니다!
In this Kamelet you can avoid using explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
The order of evaluation for Default Credentials Provider is the following:
-
Java system properties -
aws.accessKeyIdandaws.secretKey. -
Environment variables -
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY. - Web Identity Token from AWS STS.
- The shared credentials and config files.
-
Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable
AWS_CONTAINER_CREDENTIALS_RELATIVE_URIis set. - Amazon EC2 Instance profile credentials.
You can also use the Profile Credentials Provider, by setting the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
Only one of access key/secret key or default credentials provider could be used
For more information, see the AWS credentials documentation
12.2. 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 or Amazon Resource Name (ARN). | string | ||
| region * | AWS Region | The AWS region to access. | string | ||
| accessKey | Access Key | The access key obtained from AWS. | string | ||
| amazonAWSHost | AWS Host | The hostname of the Amazon AWS cloud. | string | amazonaws.com | |
| autoCreateQueue | Autocreate Queue | Automatically create the SQS queue. | boolean | False | |
| overrideEndpoint | Endpoint Overwrite |
Select this option to override the endpoint URI. To use this option, you must also provide a URI for the | boolean | False | |
| profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter sets the profile name. | string | ||
| protocol | Protocol | The underlying protocol used to communicate with SQS. | string | https | http or https |
| secretKey | Secret Key | The secret key obtained from AWS. | string | ||
| sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. | string | ||
| uriEndpointOverride | Overwrite Endpoint URI |
The overriding endpoint URI. To use this option, you must also select the | string | ||
| 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). | boolean | False | |
| useProfileCredentialsProvider | Profile Credentials Provider | Set whether the SQS client should expect to load credentials through a profile credentials provider. | boolean | False | |
| 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 | False |
* = Fields marked with an asterisk are mandatory.
12.3. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
12.3.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
12.4. Usage 링크 복사링크가 클립보드에 복사되었습니다!
12.4.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
12.4.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
12.4.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
12.4.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-sqs-sink Kamelet as a Knative sink by binding it to a Knative object.
aws-sqs-sink-binding.yaml
12.4.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-sqs-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
aws-sqs-sink-binding.yaml
12.5. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 13. AWS SQS Source 링크 복사링크가 클립보드에 복사되었습니다!
Receive data from AWS SQS.
13.1. Authentication methods 링크 복사링크가 클립보드에 복사되었습니다!
In this Kamelet you can avoid using explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
The order of evaluation for Default Credentials Provider is the following:
-
Java system properties -
aws.accessKeyIdandaws.secretKey. -
Environment variables -
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY. - Web Identity Token from AWS STS.
- The shared credentials and config files.
-
Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable
AWS_CONTAINER_CREDENTIALS_RELATIVE_URIis set. - Amazon EC2 Instance profile credentials.
You can also use the Profile Credentials Provider, by setting the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
Only one of access key/secret key or default credentials provider could be used
For more information, see the AWS credentials documentation
13.2. 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. | string | ||
| region * | AWS Region | The AWS region to access. | string | ||
| accessKey | Access Key | The access key obtained from AWS. | string | ||
| amazonAWSHost | AWS Host | The hostname of the Amazon AWS cloud. | string | amazonaws.com | |
| autoCreateQueue | Autocreate Queue | Setting the autocreation of the SQS queue. | boolean | False | |
| delay | Delay | The number of milliseconds before the next poll of the selected stream. | integer | 500 | |
| deleteAfterRead | Auto-delete Messages | Delete messages after consuming them. | boolean | True | |
| greedy | Greedy Scheduler | If greedy is enabled, then the polling will happen immediately again, if the previous run polled 1 or more messages. | boolean | False | |
| 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. | integer | 1 | |
| overrideEndpoint | Endpoint Overwrite |
Select this option to override the endpoint URI. To use this option, you must also provide a URI for the | boolean | False | |
| profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter sets the profile name. | string | ||
| protocol | Protocol | The underlying protocol used to communicate with SQS. | string | https | http or https |
| queueURL | Queue URL | The full SQS Queue URL (required if using KEDA). | string | ||
| secretKey | Secret Key | The secret key obtained from AWS. | string | ||
| sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. | string | ||
| uriEndpointOverride | Overwrite Endpoint URI |
The overriding endpoint URI. To use this option, you must also select the | string | ||
| 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). | boolean | False | |
| useProfileCredentialsProvider | Profile Credentials Provider | Set whether the SQS client should expect to load credentials through a profile credentials provider. | boolean | False | |
| 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 | False | |
| visibilityTimeout | Visibility Timeout | The duration (in seconds) that the received messages are hidden from subsequent retrieve requests after being retrieved by a ReceiveMessage request. | integer | ||
| 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. | integer |
* = Fields marked with an asterisk are mandatory.
13.3. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
13.3.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
13.4. Usage 링크 복사링크가 클립보드에 복사되었습니다!
13.4.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
13.4.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
13.4.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
13.4.2. Knative Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-sqs-source Kamelet as a Knative source by binding it to a Knative object.
aws-sqs-source-binding.yaml
13.4.3. Kafka Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-sqs-source Kamelet as a Kafka source by binding it to a Kafka topic.
aws-sqs-source-binding.yaml
13.5. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 14. AWS SQS FIFO Sink 링크 복사링크가 클립보드에 복사되었습니다!
Send message to an AWS SQS FIFO Queue.
14.1. Authentication methods 링크 복사링크가 클립보드에 복사되었습니다!
In this Kamelet you can avoid using explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
The order of evaluation for Default Credentials Provider is the following:
-
Java system properties -
aws.accessKeyIdandaws.secretKey. -
Environment variables -
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY. - Web Identity Token from AWS STS.
- The shared credentials and config files.
-
Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable
AWS_CONTAINER_CREDENTIALS_RELATIVE_URIis set. - Amazon EC2 Instance profile credentials.
You can also use the Profile Credentials Provider, by setting the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
Only one of access key/secret key or default credentials provider could be used
For more information, see the AWS credentials documentation
14.2. 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 | string | ||
| region * | AWS Region | The AWS region to access. | string | ||
| accessKey | Access Key | The access key obtained from AWS. | string | ||
| amazonAWSHost | AWS Host | The hostname of the Amazon AWS cloud. | string | amazonaws.com | |
| autoCreateQueue | Autocreate Queue | Setting the autocreation of the SQS queue. | boolean | False | |
| contentBasedDeduplication | Content-Based Deduplication | Use content-based deduplication (should be enabled in the SQS FIFO queue first) | boolean | False | |
| overrideEndpoint | Endpoint Overwrite |
Select this option to override the endpoint URI. To use this option, you must also provide a URI for the | boolean | False | |
| profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter sets the profile name. | string | ||
| protocol | Protocol | The underlying protocol used to communicate with SQS | string | https | http or https |
| secretKey | Secret Key | The secret key obtained from AWS. | string | ||
| sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. | string | ||
| uriEndpointOverride | Overwrite Endpoint URI |
The overriding endpoint URI. To use this option, you must also select the | 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 | False | |
| useProfileCredentialsProvider | Profile Credentials Provider | Set whether the SQS client should expect to load credentials through a profile credentials provider. | boolean | False | |
| 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 | False |
* = Fields marked with an asterisk are mandatory.
14.3. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
14.3.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
14.4. Usage 링크 복사링크가 클립보드에 복사되었습니다!
14.4.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
14.4.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
14.4.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
14.4.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-sqs-fifo-sink Kamelet as a Knative sink by binding it to a Knative object.
aws-sqs-fifo-sink-binding.yaml
14.4.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-sqs-fifo-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
aws-sqs-fifo-sink-binding.yaml
14.5. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 15. AWS S3 Sink 링크 복사링크가 클립보드에 복사되었습니다!
Upload data to an Amazon S3 Bucket.
15.1. Authentication methods 링크 복사링크가 클립보드에 복사되었습니다!
In this Kamelet you can avoid using explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
The order of evaluation for Default Credentials Provider is the following:
-
Java system properties -
aws.accessKeyIdandaws.secretKey. -
Environment variables -
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY. - Web Identity Token from AWS STS.
- The shared credentials and config files.
-
Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable
AWS_CONTAINER_CREDENTIALS_RELATIVE_URIis set. - Amazon EC2 Instance profile credentials.
You can also use the Profile Credentials Provider, by setting the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
Only one of access key/secret key or default credentials provider could be used
For more information, see the AWS credentials documentation
15.2. Optional Headers 링크 복사링크가 클립보드에 복사되었습니다!
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.
15.3. 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 Amazon Resource Name (ARN). | string | ||
| region * | AWS Region | The AWS region to access. | string | ||
| accessKey | Access Key | The access key obtained from AWS. | string | ||
| autoCreateBucket | Autocreate Bucket | Specifies to automatically create the S3 bucket. | boolean | False | |
| forcePathStyle | Force Path Style | Forces path style when accessing AWS S3 buckets. | boolean | False | |
| keyName | Key Name | The key name for saving an element in the bucket. | 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 | False | |
| profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter sets the profile name. | string | ||
| secretKey | Secret Key | The secret key obtained from AWS. | string | ||
| sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. | string | ||
| uriEndpointOverride | Overwrite Endpoint URI |
The overriding endpoint URI. To use this option, you must also select the | string | ||
| 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 | False | |
| useProfileCredentialsProvider | Profile Credentials Provider | Set whether the S3 client should expect to load credentials through a profile credentials provider. | boolean | False | |
| 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 | False |
* = Fields marked with an asterisk are mandatory.
15.4. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
15.4.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
15.5. Usage 링크 복사링크가 클립보드에 복사되었습니다!
15.5.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
15.5.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
15.5.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
15.5.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-s3-sink Kamelet as a Knative sink by binding it to a Knative object.
aws-s3-sink-binding.yaml
15.5.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-s3-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
aws-s3-sink-binding.yaml
15.6. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 16. AWS S3 Source 링크 복사링크가 클립보드에 복사되었습니다!
Receive data from an Amazon S3 Bucket.
The basic authentication method for the S3 service is to specify an access key and a secret key. These parameters are optional because the Kamelet provides a default credentials provider.
If you use the default credentials provider, the S3 client loads the credentials through this provider and doesn’t use the basic authentication method.
Two headers are duplicated with different names for clarity at sink level. CamelAwsS3Key is duplicated into aws.s3.key and CamelAwsS3BucketName is duplicated in aws.s3.bucket.name.
16.1. Authentication methods 링크 복사링크가 클립보드에 복사되었습니다!
In this Kamelet you can avoid using explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
The order of evaluation for Default Credentials Provider is the following:
-
Java system properties -
aws.accessKeyIdandaws.secretKey. -
Environment variables -
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY. - Web Identity Token from AWS STS.
- The shared credentials and config files.
-
Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable
AWS_CONTAINER_CREDENTIALS_RELATIVE_URIis set. - Amazon EC2 Instance profile credentials.
You can also use the Profile Credentials Provider, by setting the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
Only one of access key/secret key or default credentials provider could be used
For more information, see the AWS credentials documentation
16.2. Usage examples 링크 복사링크가 클립보드에 복사되었습니다!
You could consume the bucket content and directly delete the object once consumed
This kind of approach ensures that the object is consumed just one time and after the consumption it is deleted from the S3 bucket.
The deleteAfterRead property is true by default.
If you set the property to false you’ll consume the same set of objects multiple times and you’ll have to deal with managing the situation.
The ignoreBody option is set to false by default, but you can enable it. With that option set you’re going to ignore the file payload and just consume the object metadata.
You could also define a prefix parameter. With that set you’re going to consume only files starting with that prefix. As an example you could have:
By using the prefix foo/ the files consumed will only come from the folder named foo.
16.3. 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 Amazon Resource Name (ARN). | string | ||
| region * | AWS Region | The AWS region to access. | string | ||
| accessKey | Access Key | The access key obtained from AWS. | string | ||
| autoCreateBucket | Autocreate Bucket | Specifies to automatically create the S3 bucket. | boolean | False | |
| delay | Delay | The number of milliseconds before the next poll of the selected bucket. | integer | 500 | |
| deleteAfterRead | Auto-delete Objects | Specifies to delete objects after consuming them. | boolean | True | |
| 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 | ||
| forcePathStyle | Force Path Style | Forces path style when accessing AWS S3 buckets. | boolean | False | |
| ignoreBody | Ignore Body |
If true, the S3 Object body is ignored. Setting this to true overrides any behavior defined by the | boolean | False | |
| 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 | 10 | |
| moveAfterRead | Move Objects After Delete | Move objects from S3 bucket to a different bucket after they have been retrieved. | boolean | False | |
| overrideEndpoint | Endpoint Overwrite |
Select this option to override the endpoint URI. To use this option, you must also provide a URI for the | boolean | False | |
| prefix | Prefix | The AWS S3 bucket prefix to consider while searching. | string | folder/ | |
| profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter sets the profile name. | string | ||
| secretKey | Secret Key | The secret key obtained from AWS. | string | ||
| sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. | string | ||
| uriEndpointOverride | Overwrite Endpoint URI |
The overriding endpoint URI. To use this option, you must also select the | string | ||
| 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 | False | |
| useProfileCredentialsProvider | Profile Credentials Provider | Set whether the S3 client should expect to load credentials through a profile credentials provider. | boolean | False | |
| 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 | False |
* = Fields marked with an asterisk are mandatory.
16.4. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
16.4.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
16.5. Usage 링크 복사링크가 클립보드에 복사되었습니다!
16.5.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
16.5.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
16.5.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
16.5.2. Knative Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-s3-source Kamelet as a Knative source by binding it to a Knative object.
aws-s3-source-binding.yaml
16.5.3. Kafka Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-s3-source Kamelet as a Kafka source by binding it to a Kafka topic.
aws-s3-source-binding.yaml
16.6. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 17. AWS S3 Streaming upload Sink 링크 복사링크가 클립보드에 복사되었습니다!
Upload data to AWS S3 in streaming upload mode.
17.1. Authentication methods 링크 복사링크가 클립보드에 복사되었습니다!
In this Kamelet you can avoid using explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
The order of evaluation for Default Credentials Provider is the following:
-
Java system properties -
aws.accessKeyIdandaws.secretKey. -
Environment variables -
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY. - Web Identity Token from AWS STS.
- The shared credentials and config files.
-
Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable
AWS_CONTAINER_CREDENTIALS_RELATIVE_URIis set. - Amazon EC2 Instance profile credentials.
You can also use the Profile Credentials Provider, by setting the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
Only one of access key/secret key or default credentials provider could be used
For more information, see the AWS credentials documentation
17.2. Optional Headers 링크 복사링크가 클립보드에 복사되었습니다!
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.3. Configuration Options 링크 복사링크가 클립보드에 복사되었습니다!
The following table summarizes the configuration options available for the aws-s3-streaming-upload-sink Kamelet:
| Property | Name | Description | Type | Default | Example |
|---|---|---|---|---|---|
| bucketNameOrArn * | Bucket Name | The S3 Bucket name or Amazon Resource Name (ARN).. | string | ||
| keyName * | Key Name | Setting the key name for an element in the bucket through endpoint parameter. In Streaming Upload, with the default configuration, this is the base for the progressive creation of files. | string | ||
| region * | AWS Region | The AWS region to access. | string | ||
| accessKey | Access Key | The access key obtained from AWS. | string | ||
| autoCreateBucket | Autocreate Bucket | Setting the autocreation of the S3 bucket bucketName. | boolean | False | |
| batchMessageNumber | Batch Message Number | The number of messages composing a batch in streaming upload mode. | integer | 10 | |
| batchSize | Batch Size | The batch size (in bytes) in streaming upload mode. | integer | 1000000 | |
| forcePathStyle | Force Path Style | Forces path style when accessing AWS S3 buckets. | boolean | False | |
| 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 | |
| overrideEndpoint | Endpoint Overwrite |
Select this option to override the endpoint URI. To use this option, you must also provide a URI for the | boolean | False | |
| profileCredentialsName | Profile Credentials Name | If using a profile credentials provider this parameter sets the profile name. | string | ||
| restartingPolicy | Restarting Policy |
The restarting policy to use in streaming upload mode. There are 2 enums and the value can be one of | string | lastPart | |
| secretKey | Secret Key | The secret key obtained from AWS. | string | ||
| sessionToken | Session Token | Amazon AWS Session Token used when the user needs to assume a IAM role. | string | ||
| streamingUploadTimeout | Streaming Upload Timeout | While streaming upload mode is true, this option set the timeout to complete upload. | integer | ||
| uriEndpointOverride | Overwrite Endpoint URI |
The overriding endpoint URI. To use this option, you must also select the | 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 | False | |
| useProfileCredentialsProvider | Profile Credentials Provider | Set whether the S3 client should expect to load credentials through a profile credentials provider. | boolean | False | |
| 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 | False |
* = Fields marked with an asterisk are mandatory.
17.4. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
17.4.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
17.5. Usage 링크 복사링크가 클립보드에 복사되었습니다!
17.5.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
17.5.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
17.5.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
17.5.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-s3-streaming-upload-sink Kamelet as a Knative sink by binding it to a Knative object.
aws-s3-streaming-upload-sink-binding.yaml
17.5.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the aws-s3-streaming-upload-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
aws-s3-streaming-upload-sink-binding.yaml
17.6. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 18. Cassandra Sink 링크 복사링크가 클립보드에 복사되었습니다!
Send data to an Apache Cassandra cluster.
This Kamelet expects JSON Array formatted data. The content of the JSON Array is used as input for the CQL Prepared Statement set in the query parameter.
18.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 | The hostname(s) for the Cassandra server(s). Use a comma to separate multiple hostnames. | string | localhost | |
| connectionPort * | Connection Port | The port number(s) of the cassandra server(s). Use a comma to separate multiple port numbers. | string | 9042 | |
| keyspace * | Keyspace | The keyspace to use. | string | customers | |
| query * | Query | The query to execute against the Cassandra cluster table. | string | ||
| consistencyLevel | Consistency Level | The consistency level to use. | string | ANY | |
| 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 | True | |
| password | Password | The password for accessing a secured Cassandra cluster. | string | ||
| prepareStatements | Prepare Statements | If true, specifies to use PreparedStatements as the query. If false, specifies to use regular Statements as the query. | boolean | True | |
| username | Username | The username for accessing a secured Cassandra cluster. | string |
* = Fields marked with an asterisk are mandatory.
18.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
18.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
18.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
18.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
18.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
18.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
18.3.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the cassandra-sink Kamelet as a Knative sink by binding it to a Knative object.
cassandra-sink-binding.yaml
18.3.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the cassandra-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
cassandra-sink-binding.yaml
18.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 19. Cassandra Source 링크 복사링크가 클립보드에 복사되었습니다!
Send a query to an Apache Cassandra cluster table.
19.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 | The hostname(s) for the Cassandra server(s). Use a comma to separate multiple hostnames. | string | localhost | |
| connectionPort * | Connection Port | The port number(s) of the cassandra server(s). Use a comma to separate multiple port numbers. | string | 9042 | |
| keyspace * | Keyspace | The keyspace to use. | string | customers | |
| query * | Query | The query to execute against the Cassandra cluster table. | string | ||
| consistencyLevel | Consistency Level | The consistency level to use. | string | QUORUM | |
| extraTypeCodecs | Extra Type Codecs | To use a specific comma separated list of Extra Type codecs. | string | ||
| password | Password | The password for accessing a secured Cassandra cluster. | string | ||
| resultStrategy | Result Strategy | The strategy to convert the result set of the query. | string | ALL | |
| username | Username | The username for accessing a secured Cassandra cluster. | string |
* = Fields marked with an asterisk are mandatory.
19.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
19.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
19.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
19.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
19.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
19.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
19.3.2. Knative Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the cassandra-source Kamelet as a Knative source by binding it to a Knative object.
cassandra-source-binding.yaml
19.3.3. Kafka Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the cassandra-source Kamelet as a Kafka source by binding it to a Kafka topic.
cassandra-source-binding.yaml
19.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 20. 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.
20.1. Configuration Options 링크 복사링크가 클립보드에 복사되었습니다!
The following table summarizes the configuration options available for the ceph-sink Kamelet:
| Property | Name | Description | Type | Default | Example |
|---|---|---|---|---|---|
| accessKey * | Access Key | The access key. | string | ||
| bucketName * | Bucket Name | The Ceph Bucket name. | string | ||
| cephUrl * | Ceph Url Address | Set the Ceph Object Storage Address Url. | string | ||
| secretKey * | Secret Key | The secret key. | string | ||
| zoneGroup * | Bucket Zone Group | The bucket zone group. | string | ||
| autoCreateBucket | Autocreate Bucket | Specifies to automatically create the bucket. | boolean | False | |
| keyName | Key Name | The key name for saving an element in the bucket. | string |
* = Fields marked with an asterisk are mandatory.
20.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
20.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
20.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
20.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
20.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
20.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
20.3.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the ceph-sink Kamelet as a Knative sink by binding it to a Knative object.
ceph-sink-binding.yaml
20.3.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the ceph-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
ceph-sink-binding.yaml
20.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 21. Ceph Source 링크 복사링크가 클립보드에 복사되었습니다!
Receive data from an Ceph Bucket, managed by a Object Storage Gateway.
21.1. Configuration Options 링크 복사링크가 클립보드에 복사되었습니다!
The following table summarizes the configuration options available for the ceph-source Kamelet:
| Property | Name | Description | Type | Default | Example |
|---|---|---|---|---|---|
| accessKey * | Access Key | The access key. | string | ||
| bucketName * | Bucket Name | The Ceph Bucket name. | string | ||
| cephUrl * | Ceph Url Address | Set the Ceph Object Storage Address Url. | string | ||
| secretKey * | Secret Key | The secret key. | string | ||
| zoneGroup * | Bucket Zone Group | The bucket zone group. | string | ||
| autoCreateBucket | Autocreate Bucket | Specifies to automatically create the bucket. | boolean | False | |
| delay | Delay | The number of milliseconds before the next poll of the selected bucket. | integer | 500 | |
| deleteAfterRead | Auto-delete Objects | Specifies to delete objects after consuming them. | boolean | True | |
| ignoreBody | Ignore Body |
If true, the Object body is ignored. Setting this to true overrides any behavior defined by the | boolean | False | |
| 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. | boolean | True | |
| prefix | Prefix | The bucket prefix to consider while searching. | string | folder/ |
* = Fields marked with an asterisk are mandatory.
21.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
21.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
21.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
21.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
21.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
21.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
21.3.2. Knative Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the ceph-source Kamelet as a Knative source by binding it to a Knative object.
ceph-source-binding.yaml
21.3.3. Kafka Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the ceph-source Kamelet as a Kafka source by binding it to a Kafka topic.
ceph-source-binding.yaml
21.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 22. ElasticSearch Index Sink 링크 복사링크가 클립보드에 복사되었습니다!
Stores JSON-formatted data into ElasticSearch.
The input data must be formatted in JSON according to the requirements of the index.
If you specify the certificate property, you must base64 encode it before you pass it as a parameter.
In the header, you can set the following properties:
-
indexId/ce-indexid: The index ID for ElasticSearch. -
indexName/ce-indexname: The index name for ElasticSearch.
If you do not set a property in the header, the Kamelet uses the exchange ID for the index setting.
22.1. Configuration Options 링크 복사링크가 클립보드에 복사되었습니다!
The following table summarizes the configuration options available for the elasticsearch-index-sink Kamelet:
| Property | Name | Description | Type | Default | Example |
|---|---|---|---|---|---|
| clusterName * | ElasticSearch Cluster Name | The name of the ElasticSearch cluster. | string | quickstart | |
| hostAddresses * | Host Addresses |
A comma-separated list of remote transport addresses in | string | quickstart-es-http:9200 | |
| certificate | Certificate | The Certificate for accessing the Elasticsearch cluster. You must encode this value in base64. | string | ||
| enableSSL | Enable SSL | Specifies to connect by using SSL. | boolean | True | |
| indexName | Index in ElasticSearch | The name of the ElasticSearch index. | string | data | |
| password | Password | The password to connect to ElasticSearch. | string | ||
| user | Username | The username to connect to ElasticSearch. | string |
* = Fields marked with an asterisk are mandatory.
22.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
22.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
22.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
22.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
22.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
22.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
22.3.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the elasticsearch-index-sink Kamelet as a Knative sink by binding it to a Knative object.
elasticsearch-index-sink-binding.yaml
22.3.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the elasticsearch-index-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
elasticsearch-index-sink-binding.yaml
22.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 23. Extract Field Action 링크 복사링크가 클립보드에 복사되었습니다!
Extract a field from the message body.
The extract field action expects an application/json content type.
The field parameter specifies which field in the JSON to extract. By default, the message body is overridden with the extracted field.
The optional parameter headerOutput specifies whether the extracted field should be stored in a message header named 'CamelKameletsExtractFieldName', leaving the message body untouched.
The optional parameter headerOutputName specifies a custom header name instead of the default 'CamelKameletsExtractFieldName'. This parameter must be used in conjunction with headerOutput. If no headerOutputName parameter is provided, the default 'CamelKameletsExtractFieldName' is used.
The optional parameter strictHeaderCheck enables a strict header name check. If enabled, the action checks if the header output name (custom or default) is already used in the exchange. If so, the extracted field is stored in the message body, if not, the extracted field is stored in the selected header (custom or default).
The headerOutput/headerOutputName/strictHeaderCheck parameters are particulary useful in case you would like to reuse an extracted field as parameter for another header, for example.
23.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 extract | string | ||
| headerOutput | Header Output | If enable the action will store the extracted field in an header named CamelKameletsExtractFieldName | boolean | False | |
| headerOutputName | Header Output Name | A custom name for the header containing the extracted field | string | none | |
| 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 is stored in the message body, if not, the extracted field is stored in the selected header (custom or default). | boolean | False | |
| trimField | Trim Field | If enabled we return the Raw extracted field | boolean | False |
* = Fields marked with an asterisk are mandatory.
23.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
23.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
23.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
23.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
23.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
23.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
23.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the extract-field-action Kamelet as an intermediate step in a Knative binding.
extract-field-action-binding.yaml
23.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the extract-field-action Kamelet as an intermediate step in a Kafka binding.
extract-field-action-binding.yaml
23.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 24. FTP Sink 링크 복사링크가 클립보드에 복사되었습니다!
Send data to an FTP server.
In the header, you can set the file / ce-file property to specify the filename to upload.
If you do not set the property in the header, the Kamelet uses the exchange ID for the filename.
24.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 | The hostname of the FTP server. | string | ||
| connectionPort * | Connection Port | The port of the FTP server. | string | 21 | |
| directoryName * | Directory Name | The starting directory. | string | ||
| password * | Password | The password to access the FTP server. | string | ||
| username * | Username | The username to access the FTP server. | string | ||
| autoCreate | Autocreate Missing Directories | Automatically create the directory the files should be written to. | boolean | True | |
| binary | Binary | Specifies the file transfer mode, BINARY or ASCII. Default is ASCII (false). | boolean | False | |
| fileExist | File Existence | How to behave in case of file already existent. | string | Override | |
| passiveMode | Passive Mode | Specifies to use passive mode connection. | boolean | False |
* = Fields marked with an asterisk are mandatory.
24.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
24.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
24.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
24.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
24.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
24.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
24.3.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the ftp-sink Kamelet as a Knative sink by binding it to a Knative object.
ftp-sink-binding.yaml
24.3.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the ftp-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
ftp-sink-binding.yaml
24.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 25. FTP Source 링크 복사링크가 클립보드에 복사되었습니다!
Receive data from an FTP server.
25.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 | The hostname of the FTP server. | string | ||
| connectionPort * | Connection Port | The port of the FTP server. | string | 21 | |
| directoryName * | Directory Name | The starting directory | string | ||
| password * | Password | The password to access the FTP server. | string | ||
| username * | Username | The username to access the FTP server. | string | ||
| autoCreate | Autocreate Missing Directories | Automatically create starting directory. | boolean | True | |
| binary | Binary | Specifies the file transfer mode, BINARY or ASCII. Default is ASCII (false). | boolean | False | |
| delete | Delete | If true, the file is deleted after it is processed successfully. | boolean | False | |
| idempotent | Idempotency | Skip already-processed files. | boolean | True | |
| passiveMode | Passive Mode | Specifes to use passive mode connection. | boolean | False | |
| recursive | Recursive | If a directory, look for files in all the sub-directories as well. | boolean | False |
* = Fields marked with an asterisk are mandatory.
25.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
25.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
25.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
25.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
25.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
25.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
25.3.2. Knative Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the ftp-source Kamelet as a Knative source by binding it to a Knative object.
ftp-source-binding.yaml
25.3.3. Kafka Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the ftp-source Kamelet as a Kafka source by binding it to a Kafka topic.
ftp-source-binding.yaml
25.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 26. FTPS Sink 링크 복사링크가 클립보드에 복사되었습니다!
Send data to an FTPS server.
In the header, you can set the file / ce-file property to specify the filename to upload.
If you do not set the property in the header, the Kamelet uses the exchange ID for the filename.
26.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 | The hostname of the FTP server. | string | ||
| connectionPort * | Connection Port | The port of the FTP server. | string | 21 | |
| directoryName * | Directory Name | The starting directory. | string | ||
| password * | Password | The password to access the FTP server. | string | ||
| username * | Username | The username to access the FTP server. | string | ||
| autoCreate | Autocreate Missing Directories | Automatically create the directory the files should be written to. | boolean | True | |
| binary | Binary | Specifies the file transfer mode, BINARY or ASCII. Default is ASCII (false). | boolean | False | |
| fileExist | File Existence | Specifies how the Kamelet behaves if the file already exists. | string | Override | |
| passiveMode | Passive Mode | Set the passive mode connection. | boolean | False |
* = Fields marked with an asterisk are mandatory.
26.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
26.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
26.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
26.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
26.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
26.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
26.3.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the ftps-sink Kamelet as a Knative sink by binding it to a Knative object.
ftps-sink-binding.yaml
26.3.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the ftps-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
ftps-sink-binding.yaml
26.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 27. FTPS Source 링크 복사링크가 클립보드에 복사되었습니다!
Receive data from an FTPS server.
27.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 | The hostname of the FTPS server. | string | ||
| connectionPort * | Connection Port | The port of the FTPS server. | string | 21 | |
| directoryName * | Directory Name | The starting directory. | string | ||
| password * | Password | The password to access the FTPS server. | string | ||
| username * | Username | The username to access the FTPS server. | string | ||
| autoCreate | Autocreate Missing Directories | Automatically create starting directory. | boolean | True | |
| binary | Binary | Specifies the file transfer mode, BINARY or ASCII. Default is ASCII (false). | boolean | False | |
| delete | Delete | If true, the file is deleted after it is processed successfully. | boolean | False | |
| idempotent | Idempotency | Skip already-processed files. | boolean | True | |
| passiveMode | Passive Mode | Specifies to use passive mode connection. | boolean | False | |
| recursive | Recursive | If a directory, look for files in all sub-directories as well. | boolean | False |
* = Fields marked with an asterisk are mandatory.
27.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
27.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
27.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
27.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
27.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
27.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
27.3.2. Knative Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the ftps-source Kamelet as a Knative source by binding it to a Knative object.
ftps-source-binding.yaml
27.3.3. Kafka Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the ftps-source Kamelet as a Kafka source by binding it to a Kafka topic.
ftps-source-binding.yaml
27.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 28. Has Header Filter Action 링크 복사링크가 클립보드에 복사되었습니다!
Filter message based on the presence of one header.
28.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, the name of the header requires a CloudEvent (ce-) prefix. | string | headerName | |
| value | Header Value | An optional header value to compare the header to | string | headerValue |
* = Fields marked with an asterisk are mandatory.
28.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
28.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
28.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
28.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
28.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
28.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
28.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the has-header-filter-action Kamelet as an intermediate step in a Knative binding.
has-header-filter-action-binding.yaml
28.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the has-header-filter-action Kamelet as an intermediate step in a Kafka binding.
has-header-filter-action-binding.yaml
28.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 29. Hoist Field Action 링크 복사링크가 클립보드에 복사되었습니다!
Wrap data in a single field.
29.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. | string |
* = Fields marked with an asterisk are mandatory.
29.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
29.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
29.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
29.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
29.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
29.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
29.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the hoist-field-action Kamelet as an intermediate step in a Knative binding.
hoist-field-action-binding.yaml
29.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the hoist-field-action Kamelet as an intermediate step in a Kafka binding.
hoist-field-action-binding.yaml
29.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 30. HTTP Sink 링크 복사링크가 클립보드에 복사되었습니다!
Forward data to a HTTP or HTTPS endpoint.
30.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 which you want to send data. | string | ||
| method | Method | The HTTP method to use. | string | POST |
* = Fields marked with an asterisk are mandatory.
30.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
30.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
30.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
30.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
30.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
30.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
30.3.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the http-sink Kamelet as a Knative sink by binding it to a Knative object.
http-sink-binding.yaml
30.3.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the http-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
http-sink-binding.yaml
30.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 31. Insert Field Action 링크 복사링크가 클립보드에 복사되었습니다!
Adds a custom field with a simple language parsed value to the message in transit.
The insert field action expects an application/json content type.
For example, if you have an object like { "foo":"John", "bar":30 }, and your action is configured with the field element and the value hello, the result is { "foo":"John", "bar":30, "element":"hello" }.
31.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. | string | ||
| value * | Value | The value of the field. | string |
* = Fields marked with an asterisk are mandatory.
31.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
31.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
31.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
31.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
31.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
31.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
31.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the insert-field-action Kamelet as an intermediate step in a Knative binding.
insert-field-action-binding.yaml
31.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the insert-field-action Kamelet as an intermediate step in a Kafka binding.
insert-field-action-binding.yaml
31.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 32. Insert Header Action 링크 복사링크가 클립보드에 복사되었습니다!
Adds an header with a simple language parsed expression to the message in transit.
32.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. | string | headername | |
| value * | Value | The value of the header to be added | string |
* = Fields marked with an asterisk are mandatory.
32.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
32.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
32.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
32.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
32.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
32.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
32.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You must use the insert-header-action Kamelet as an intermediate step in a Knative binding.
insert-header-action-binding.yaml
32.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You must use the insert-header-action Kamelet as an intermediate step in a Kafka binding.
insert-header-action-binding.yaml
32.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 33. Is Tombstone Filter Action 링크 복사링크가 클립보드에 복사되었습니다!
Filter based on the presence of body or not.
33.1. Configuration Options 링크 복사링크가 클립보드에 복사되었습니다!
The is-tombstone-filter-action Kamelet does not have any options.
33.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
33.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
33.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
33.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
33.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
33.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
33.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the is-tombstone-filter-action Kamelet as an intermediate step in a Knative binding.
is-tombstone-filter-action-binding.yaml
33.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the is-tombstone-filter-action Kamelet as an intermediate step in a Kafka binding.
is-tombstone-filter-action-binding.yaml
33.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 34. 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.
To authenticate, a username/password or personal token must be defined. We recommend to use personal token as it is a safer way to get access to Jira.
34.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 | string | ||
| password | Password | The password to access Jira | string | ||
| personal-token | Personal Token | Personal Token | string | ||
| username | Username | The username to access Jira | string |
* = Fields marked with an asterisk are mandatory.
34.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
34.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
34.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
34.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
34.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
34.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
34.3.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the jira-add-comment-sink Kamelet as a Knative sink by binding it to a Knative object.
jira-add-comment-sink-binding.yaml
34.3.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the jira-add-comment-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
jira-add-comment-sink-binding.yaml
34.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 35. 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.
To authenticate, a username/password or personal token must be defined. We recommend to use personal token as it is a safer way to get access to Jira.
35.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 | string | ||
| password | Password | The password to access Jira | string | ||
| personal-token | Personal Token | Personal Token | string | ||
| username | Username | The username to access Jira | string |
* = Fields marked with an asterisk are mandatory.
35.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
35.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
35.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
35.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
35.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
35.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
35.3.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the jira-add-issue-sink Kamelet as a Knative sink by binding it to a Knative object.
jira-add-issue-sink-binding.yaml
35.3.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the jira-add-issue-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
jira-add-issue-sink-binding.yaml
35.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 36. 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.
To authenticate, a username/password or personal token must be defined. We recommend to use personal token as it is a safer way to get access to Jira.
36.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 | string | ||
| password | Password | The password to access Jira | string | ||
| personal-token | Personal Token | Personal Token | string | ||
| username | Username | The username to access Jira | string |
* = Fields marked with an asterisk are mandatory.
36.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
36.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
36.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
36.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
36.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
36.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
36.3.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the jira-transition-issue-sink Kamelet as a Knative sink by binding it to a Knative object.
jira-transition-issue-sink-binding.yaml
36.3.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the jira-transition-issue-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
jira-transition-issue-sink-binding.yaml
36.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 37. 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.
To authenticate, a username/password or personal token must be defined. We recommend to use personal token as it is a safer way to get access to Jira.
37.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 | string | ||
| password | Password | The password to access Jira | string | ||
| personal-token | Personal Token | Personal Token | string | ||
| username | Username | The username to access Jira | string |
* = Fields marked with an asterisk are mandatory.
37.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
37.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
37.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
37.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
37.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
37.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
37.3.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the jira-update-issue-sink Kamelet as a Knative sink by binding it to a Knative object.
jira-update-issue-sink-binding.yaml
37.3.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the jira-update-issue-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
jira-update-issue-sink-binding.yaml
37.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 38. Jira Source 링크 복사링크가 클립보드에 복사되었습니다!
Receive notifications about new issues from Jira.
To authenticate, a username/password or personal token must be defined. We recommend to use personal token as it is a safer way to get access to Jira.
38.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. | string | ||
| jql | JQL | A query to filter issues. | string | project=MyProject | |
| password | Password | The password to access Jira. | string | ||
| personal-token | Personal Token | Personal Token | string | ||
| username | Username | The username to access Jira. | string |
* = Fields marked with an asterisk are mandatory.
38.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
38.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
38.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
38.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
38.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
38.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
38.3.2. Knative Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the jira-source Kamelet as a Knative source by binding it to a Knative object.
jira-source-binding.yaml
38.3.3. Kafka Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the jira-source Kamelet as a Kafka source by binding it to a Kafka topic.
jira-source-binding.yaml
38.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 39. JMS - AMQP 1.0 Sink 링크 복사링크가 클립보드에 복사되었습니다!
Send data to any AMQP 1.0 compliant message broker by using the Apache Qpid JMS client.
39.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. | string | ||
| remoteURI * | Broker URL | The JMS URL. | string | amqp://my-host:31616 | |
| destinationType | Destination Type | The JMS destination type (queue or topic). | string | queue |
* = Fields marked with an asterisk are mandatory.
39.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
39.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
39.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
39.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
39.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
39.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
39.3.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the jms-amqp-10-sink Kamelet as a Knative sink by binding it to a Knative object.
jms-amqp-10-sink-binding.yaml
39.3.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the jms-amqp-10-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
jms-amqp-10-sink-binding.yaml
39.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 40. JMS - AMQP 1.0 Source 링크 복사링크가 클립보드에 복사되었습니다!
Consume data from any AMQP 1.0 compliant message broker by using the Apache Qpid JMS client.
40.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. | string | ||
| remoteURI * | Broker URL | The JMS URL. | string | amqp://my-host:31616 | |
| destinationType | Destination Type | The JMS destination type (queue or topic). | string | queue |
* = Fields marked with an asterisk are mandatory.
40.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
40.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
40.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
40.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
40.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
40.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
40.3.2. Knative Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the jms-amqp-10-source Kamelet as a Knative source by binding it to a Knative object.
jms-amqp-10-source-binding.yaml
40.3.3. Kafka Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the jms-amqp-10-source Kamelet as a Kafka source by binding it to a Kafka topic.
jms-amqp-10-source-binding.yaml
40.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 41. JMS - IBM MQ Sink 링크 복사링크가 클립보드에 복사되었습니다!
A Kamelet that can produce events to an IBM MQ message queue using JMS.
In your Pipe file, you must explicitly declare the IBM MQ Server driver dependency in spec→integration→dependencies:
41.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. | string | ||
| destinationName * | Destination Name | The destination name. | string | ||
| password * | Password | Password to authenticate to IBM MQ server. | string | ||
| queueManager * | IBM MQ Queue Manager | Name of the IBM MQ Queue Manager. | string | ||
| serverName * | IBM MQ Server name | IBM MQ Server name or address. | string | ||
| serverPort * | IBM MQ Server Port | IBM MQ Server port. | integer | 1414 | |
| username * | Username | Username to authenticate to IBM MQ server. | string | ||
| clientId | IBM MQ Client ID | Name of the IBM MQ Client ID. | string | ||
| destinationType | Destination Type | The JMS destination type (queue or topic). | string | queue | |
| sslCipherSuite | CipherSuite | CipherSuite to use for enabling TLS. | string |
* = Fields marked with an asterisk are mandatory.
41.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
41.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
41.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
41.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
41.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
41.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
41.3.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the jms-ibm-mq-sink Kamelet as a Knative sink by binding it to a Knative object.
jms-ibm-mq-sink-binding.yaml
41.3.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the jms-ibm-mq-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
jms-ibm-mq-sink-binding.yaml
41.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 42. JMS - IBM MQ Source 링크 복사링크가 클립보드에 복사되었습니다!
A Kamelet that can read events from an IBM MQ message queue using JMS.
In your Pipe file, you must explicitly declare the IBM MQ Server driver dependency in spec→integration→dependencies:
42.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. | string | ||
| destinationName * | Destination Name | The destination name. | string | ||
| password * | Password | Password to authenticate to IBM MQ server. | string | ||
| queueManager * | IBM MQ Queue Manager | Name of the IBM MQ Queue Manager. | string | ||
| serverName * | IBM MQ Server name | IBM MQ Server name or address. | string | ||
| serverPort * | IBM MQ Server Port | IBM MQ Server port. | integer | 1414 | |
| username * | Username | Username to authenticate to IBM MQ server. | string | ||
| clientId | IBM MQ Client ID | Name of the IBM MQ Client ID. | string | ||
| destinationType | Destination Type | The JMS destination type (queue or topic). | string | queue | |
| sslCipherSuite | CipherSuite | CipherSuite to use for enabling TLS. | string |
* = Fields marked with an asterisk are mandatory.
42.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
42.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
42.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
42.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
42.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
42.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
42.3.2. Knative Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the jms-ibm-mq-source Kamelet as a Knative source by binding it to a Knative object.
jms-ibm-mq-source-binding.yaml
42.3.3. Kafka Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the jms-ibm-mq-source Kamelet as a Kafka source by binding it to a Kafka topic.
jms-ibm-mq-source-binding.yaml
42.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 43. JSLT Action 링크 복사링크가 클립보드에 복사되었습니다!
Apply a JSLT query or transformation on JSON.
43.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 | string |
* = Fields marked with an asterisk are mandatory.
43.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
43.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
43.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
43.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
43.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
43.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
43.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the jslt-action Kamelet as an intermediate step in a Knative binding.
jslt-action-binding.yaml
43.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the jslt-action Kamelet as an intermediate step in a Kafka binding.
jslt-action-binding.yaml
43.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 44. Json Deserialize Action 링크 복사링크가 클립보드에 복사되었습니다!
Deserialize payload to JSON.
44.1. Configuration Options 링크 복사링크가 클립보드에 복사되었습니다!
The json-deserialize-action Kamelet does not have any options.
44.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
44.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
44.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
44.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
44.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
44.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
44.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the json-deserialize-action Kamelet as an intermediate step in a Knative binding.
json-deserialize-action-binding.yaml
44.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the json-deserialize-action Kamelet as an intermediate step in a Kafka binding.
json-deserialize-action-binding.yaml
44.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 45. Json Serialize Action 링크 복사링크가 클립보드에 복사되었습니다!
Serialize payload to JSON.
45.1. Configuration Options 링크 복사링크가 클립보드에 복사되었습니다!
The json-serialize-action Kamelet does not have any options.
45.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
45.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
45.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
45.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
45.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
45.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
45.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the json-serialize-action Kamelet as an intermediate step in a Knative binding.
json-serialize-action-binding.yaml
45.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the json-serialize-action Kamelet as an intermediate step in a Kafka binding.
json-serialize-action-binding.yaml
45.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 46. Kafka Batch Manual Commit Action 링크 복사링크가 클립보드에 복사되었습니다!
Manually commit Kafka Batch Offset.
46.1. Configuration Options 링크 복사링크가 클립보드에 복사되었습니다!
The kafka-batch-manual-commit-action Kamelet does not have any options.
46.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
46.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
46.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
46.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
46.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
46.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
46.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the kafka-batch-manual-commit-action Kamelet as an intermediate step in a Knative binding.
kafka-batch-manual-commit-action-binding.yaml
46.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the kafka-batch-manual-commit-action Kamelet as an intermediate step in a Kafka binding.
kafka-batch-manual-commit-action-binding.yaml
46.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 47. Kafka Batch Source 링크 복사링크가 클립보드에 복사되었습니다!
Receive data from Kafka topics in batch through Plain Login Module and commit them manually through KafkaManualCommit..
47.1. Configuration Options 링크 복사링크가 클립보드에 복사되었습니다!
The following table summarizes the configuration options available for the kafka-batch-source Kamelet:
| Property | Name | Description | Type | Default | Example |
|---|---|---|---|---|---|
| bootstrapServers * | Bootstrap Servers | Comma separated list of Kafka Broker URLs | string | ||
| password * | Password | Password to authenticate to kafka | string | ||
| topic * | Topic Names | Comma separated list of Kafka topic names | string | ||
| user * | Username | Username to authenticate to Kafka | string | ||
| allowManualCommit | Allow Manual Commit | Whether to allow doing manual commits | boolean | False | |
| autoCommitEnable | Auto Commit Enable | If true, periodically commit to ZooKeeper the offset of messages already fetched by the consumer | boolean | True | |
| 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 | latest | |
| batchSize | Batch Dimension | The maximum number of records returned in a single call to poll() | integer | 500 | |
| batchingIntervalMs | Batching Interval | In consumer batching mode, then this option is specifying a time in millis, to trigger batch completion eager when the current batch size has not reached the maximum size defined by maxPollRecords. Notice the trigger is not exact at the given interval, as this can only happen between kafka polls (see pollTimeoutMs option). | integer | ||
| consumerGroup | Consumer Group | A string that uniquely identifies the group of consumers to which this source belongs | string | my-group-id | |
| deserializeHeaders | Automatically Deserialize Headers | When enabled the Kamelet source will deserialize all message headers to String representation. | boolean | True | |
| maxPollIntervalMs | Max Poll Interval | The maximum delay between invocations of poll() when using consumer group management | integer | ||
| 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 | string | ERROR_HANDLER | |
| pollTimeout | Poll Timeout Interval | The timeout used when polling the KafkaConsumer | integer | 5000 | |
| saslMechanism | SASL Mechanism | The Simple Authentication and Security Layer (SASL) Mechanism used. | string | PLAIN | |
| securityProtocol | Security Protocol | Protocol used to communicate with brokers. SASL_PLAINTEXT, PLAINTEXT, SASL_SSL and SSL are supported | string | SASL_SSL | |
| 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 | False |
* = Fields marked with an asterisk are mandatory.
47.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
47.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
47.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
47.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
47.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
47.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
47.3.2. Knative Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the kafka-batch-source Kamelet as a Knative source by binding it to a Knative object.
kafka-batch-source-binding.yaml
47.3.3. Kafka Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the kafka-batch-source Kamelet as a Kafka source by binding it to a Kafka topic.
kafka-batch-source-binding.yaml
47.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 48. Kafka Manual Commit Action 링크 복사링크가 클립보드에 복사되었습니다!
Manually commit Kafka Offset.
48.1. Configuration Options 링크 복사링크가 클립보드에 복사되었습니다!
The kafka-manual-commit-action Kamelet does not have any options.
48.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
48.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
48.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
48.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
48.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
48.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
48.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the kafka-manual-commit-action Kamelet as an intermediate step in a Knative binding.
kafka-manual-commit-action-binding.yaml
48.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the kafka-manual-commit-action Kamelet as an intermediate step in a Kafka binding.
kafka-manual-commit-action-binding.yaml
48.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 49. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
Send data to Kafka topics through Plain Login Module.
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.
49.1. Configuration Options 링크 복사링크가 클립보드에 복사되었습니다!
The following table summarizes the configuration options available for the kafka-sink Kamelet:
| Property | Name | Description | Type | Default | Example |
|---|---|---|---|---|---|
| bootstrapServers * | Bootstrap Servers | Comma separated list of Kafka Broker URLs | string | ||
| password * | Password | Password to authenticate to kafka | string | ||
| topic * | Topic Names | Comma separated list of Kafka topic names | string | ||
| user * | Username | Username to authenticate to Kafka | string | ||
| saslMechanism | SASL Mechanism | The Simple Authentication and Security Layer (SASL) Mechanism used. | string | PLAIN | |
| securityProtocol | Security Protocol | Protocol used to communicate with brokers. SASL_PLAINTEXT, PLAINTEXT, SASL_SSL and SSL are supported | string | SASL_SSL |
* = Fields marked with an asterisk are mandatory.
49.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
49.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
49.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
49.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
49.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
49.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
49.3.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the kafka-sink Kamelet as a Knative sink by binding it to a Knative object.
kafka-sink-binding.yaml
49.3.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the kafka-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
kafka-sink-binding.yaml
49.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 50. Kafka Source 링크 복사링크가 클립보드에 복사되었습니다!
Receive data from Kafka topics through Plain Login Module.
50.1. Configuration Options 링크 복사링크가 클립보드에 복사되었습니다!
The following table summarizes the configuration options available for the kafka-source Kamelet:
| Property | Name | Description | Type | Default | Example |
|---|---|---|---|---|---|
| bootstrapServers * | Bootstrap Servers | Comma separated list of Kafka Broker URLs | string | ||
| password * | Password | Password to authenticate to kafka | string | ||
| topic * | Topic Names | Comma separated list of Kafka topic names | string | ||
| user * | Username | Username to authenticate to Kafka | string | ||
| allowManualCommit | Allow Manual Commit | Whether to allow doing manual commits | boolean | False | |
| autoCommitEnable | Auto Commit Enable | If true, periodically commit to ZooKeeper the offset of messages already fetched by the consumer | boolean | True | |
| 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 | latest | |
| consumerGroup | Consumer Group | A string that uniquely identifies the group of consumers to which this source belongs | string | my-group-id | |
| deserializeHeaders | Automatically Deserialize Headers | When enabled the Kamelet source will deserialize all message headers to String representation. | boolean | True | |
| 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 | string | ERROR_HANDLER | |
| saslMechanism | SASL Mechanism | The Simple Authentication and Security Layer (SASL) Mechanism used. | string | PLAIN | |
| securityProtocol | Security Protocol | Protocol used to communicate with brokers. SASL_PLAINTEXT, PLAINTEXT, SASL_SSL and SSL are supported | string | SASL_SSL | |
| 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 | False |
* = Fields marked with an asterisk are mandatory.
50.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
50.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
50.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
50.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
50.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
50.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
50.3.2. Knative Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the kafka-source Kamelet as a Knative source by binding it to a Knative object.
kafka-source-binding.yaml
50.3.3. Kafka Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the kafka-source Kamelet as a Kafka source by binding it to a Kafka topic.
kafka-source-binding.yaml
50.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 51. Kafka Topic Name Matches Filter Action 링크 복사링크가 클립보드에 복사되었습니다!
Filter based on kafka topic value compared to regex.
51.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 | string |
* = Fields marked with an asterisk are mandatory.
51.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
51.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
51.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
51.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 52. Log Sink 링크 복사링크가 클립보드에 복사되었습니다!
A sink that logs all data that it receives, useful for debugging purposes.
52.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 | string | log-sink | |
| level | Log Level | Logging level to use | string | INFO | |
| logMask | Log Mask | Mask sensitive information like password or passphrase in the log | boolean | False | |
| marker | Marker | An optional Marker name to use | string | ||
| multiline | Multiline | If enabled then each information is outputted on a newline | boolean | False | |
| showAllProperties | Show All Properties | Show all of the exchange properties (both internal and custom) | boolean | False | |
| showBody | Show Body | Show the message body | boolean | True | |
| showBodyType | Show Body Type | Show the body Java type | boolean | True | |
| showExchangePattern | Show Exchange Pattern | Shows the Message Exchange Pattern (or MEP for short) | boolean | True | |
| showHeaders | Show Headers | Show the headers received | boolean | False | |
| showProperties | Show Properties | Show the exchange properties (only custom). Use showAllProperties to show both internal and custom properties. | boolean | False | |
| showStreams | Show Streams | Show the stream bodies (they may not be available in following steps) | boolean | False | |
| showCachedStreams | Show Cached Streams | Whether Camel should show cached stream bodies or not. | boolean | True |
* = Fields marked with an asterisk are mandatory.
52.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
52.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
52.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
52.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
52.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
52.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
52.3.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the log-sink Kamelet as a Knative sink by binding it to a Knative object.
log-sink-binding.yaml
52.3.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the log-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
log-sink-binding.yaml
52.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 53. MariaDB Sink 링크 복사링크가 클립보드에 복사되었습니다!
Send data to a MariaDB Database.
In your Pipe file, you must explicitly declare the MariaDB Server driver dependency in spec→integration→dependencies:.
- "mvn:org.mariadb.jdbc:mariadb-java-client:<version>"
This Kamelet expects a JSON-formatted body. Use key:value pairs to map the JSON fields and parameters. For example, here is a query:
'INSERT INTO accounts (username,city) VALUES (:#username,:#city)'
Here is example input for the example query:
'{ "username":"oscerd", "city":"Rome"}'
53.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 name of the MariaDB Database. | string | ||
| password * | Password | The password to access a secured MariaDB Database. | string | ||
| query * | Query | The query to execute against the MariaDB Database. | string | INSERT INTO accounts (username,city) VALUES (:#username,:#city) | |
| serverName * | Server Name | The server name for the data source. | string | localhost | |
| username * | Username | The username to access a secured MariaDB Database. | string | ||
| serverPort | Server Port | The server port for the data source. | string | 3306 |
* = Fields marked with an asterisk are mandatory.
53.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
53.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
53.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
53.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
53.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
53.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
53.3.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the mariadb-sink Kamelet as a Knative sink by binding it to a Knative object.
mariadb-sink-binding.yaml
53.3.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the mariadb-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
mariadb-sink-binding.yaml
53.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 54. Mask Fields Action 링크 복사링크가 클립보드에 복사되었습니다!
Mask fields with a constant value in the message in transit.
54.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 | string | ||
| replacement * | Replacement | Replacement for the fields to be masked | string |
* = Fields marked with an asterisk are mandatory.
54.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
54.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
54.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
54.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
54.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
54.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
54.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the mask-field-action Kamelet as an intermediate step in a Knative binding.
mask-field-action-binding.yaml
54.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the mask-field-action Kamelet as an intermediate step in a Kafka binding.
mask-field-action-binding.yaml
54.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 55. Message Timestamp Router Action 링크 복사링크가 클립보드에 복사되었습니다!
Update the topic field as a function of the original topic name and the record’s timestamp field.
55.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. | string | ||
| timestampFormat | Timestamp Format | Format string for the timestamp that is compatible with java.text.SimpleDateFormat. | string | yyyyMMdd | |
| timestampKeyFormat | Timestamp Keys Format |
Format of the timestamp keys. Possible values are | string | timestamp | |
| topicFormat | Topic Format | Format string which can contain '$[topic]' and '$[timestamp]' as placeholders for the topic and timestamp, respectively. | string | topic-$[timestamp] |
* = Fields marked with an asterisk are mandatory.
55.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
55.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
55.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
55.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
55.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
55.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
55.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the message-timestamp-router-action Kamelet as an intermediate step in a Knative binding.
message-timestamp-router-action-binding.yaml
55.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the message-timestamp-router-action Kamelet as an intermediate step in a Kafka binding.
message-timestamp-router-action-binding.yaml
55.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 56. MongoDB Sink 링크 복사링크가 클립보드에 복사되었습니다!
Send data to MongoDB.
This Kamelet expects a JSON-formatted body.
In the header, you can set the db-upsert / ce-dbupsert property, a boolean value that specifies whether the database should create an element if it does not exist.
56.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 | The name of the MongoDB collection to bind to this endpoint. | string | ||
| database * | MongoDB Database | The name of the MongoDB database. | string | ||
| hosts * | MongoDB Hosts |
A comma-separated list of MongoDB host addresses in | string | ||
| createCollection | Collection | Create a collection during initialization if it doesn’t exist. | boolean | False | |
| password | MongoDB Password | A user password for accessing MongoDB. | string | ||
| ssl | Enable Ssl for Mongodb Connection | whether to enable ssl connection to mongodb. | boolean | True | |
| sslValidationEnabled | Enables Ssl Certificates Validation and Host name checks. | IMPORTANT this should be disabled only in test environment since can pose security issues. | boolean | True | |
| username | MongoDB Username | A username for accessing MongoDB. | string | ||
| writeConcern | Write Concern | The level of acknowledgment requested from MongoDB for write operations. | string |
* = Fields marked with an asterisk are mandatory.
56.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
56.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
56.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
56.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
56.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
56.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
56.3.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the mongodb-sink Kamelet as a Knative sink by binding it to a Knative object.
mongodb-sink-binding.yaml
56.3.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the mongodb-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
mongodb-sink-binding.yaml
56.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 57. MongoDB Source 링크 복사링크가 클립보드에 복사되었습니다!
Consume data from MongoDB.
If you enable the persistentTailTracking property, the consumer keeps track of the last consumed message and, on the next restart, the consumption restarts from that message. If you enable persistentTailTracking, you must provide a value for the tailTrackIncreasingField property (by default it is optional).
If you disable the persistentTailTracking property, the consumer consumes the whole collection and waits in idle for new data to consume.
The collection that provides the data must be a capped collection.
57.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 | The name of the MongoDB collection to bind to this endpoint. | string | ||
| database * | MongoDB Database | The name of the MongoDB database. | string | ||
| hosts * | MongoDB Hosts |
A comma-separated list of MongoDB host addresses in | string | ||
| password | MongoDB Password | The user password for accessing MongoDB. | string | ||
| persistentTailTracking | MongoDB Persistent Tail Tracking | Specifies to enable persistent tail tracking, which is a mechanism to keep track of the last consumed data across system restarts. The next time the system is up, the endpoint recovers the cursor from the point where it last stopped consuimg data. This option will only work on capped collections. | boolean | False | |
| ssl | Enable Ssl for Mongodb Connection | whether to enable ssl connection to mongodb | boolean | True | |
| sslValidationEnabled | Enables Ssl Certificates Validation and Host name checks. | IMPORTANT this should be disabled only in test environment since can pose security issues. | boolean | True | |
| tailTrackIncreasingField | MongoDB Tail Track Increasing Field | The correlation field in the incoming data which is of increasing nature and is used to position the tailing cursor every time it is generated. | string | ||
| username | MongoDB Username |
The username for accessing MongoDB. The username must be present in the MongoDB’s authentication database ( | string |
* = Fields marked with an asterisk are mandatory.
57.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
57.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
57.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
57.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
57.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
57.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
57.3.2. Knative Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the mongodb-source Kamelet as a Knative source by binding it to a Knative object.
mongodb-source-binding.yaml
57.3.3. Kafka Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the mongodb-source Kamelet as a Kafka source by binding it to a Kafka topic.
mongodb-source-binding.yaml
57.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 58. MySQL Sink 링크 복사링크가 클립보드에 복사되었습니다!
Send data to a MySQL Database.
In your Pipe file, you must explicitly declare the SQL Server driver dependency in spec→integration→dependencies:.
This Kamelet expects a JSON-formatted body. Use key:value pairs to map the JSON fields and parameters. For example, here is a query:
'INSERT INTO accounts (username,city) VALUES (:#username,:#city)'
Here is example input for the example query:
'{ "username":"oscerd", "city":"Rome"}'
58.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 name of the MySQL Database. | string | ||
| password * | Password | The password to access a secured MySQL Database. | string | ||
| query * | Query | The query to execute against the MySQL Database. | string | INSERT INTO accounts (username,city) VALUES (:#username,:#city) | |
| serverName * | Server Name | The server name for the data source. | string | localhost | |
| username * | Username | The username to access a secured MySQL Database. | string | ||
| serverPort | Server Port | The server port for the data source. | string | 3306 |
* = Fields marked with an asterisk are mandatory.
58.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
58.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
58.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
58.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
58.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
58.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
58.3.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the mysql-sink Kamelet as a Knative sink by binding it to a Knative object.
mysql-sink-binding.yaml
58.3.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the mysql-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
mysql-sink-binding.yaml
58.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 59. PostgreSQL Sink 링크 복사링크가 클립보드에 복사되었습니다!
Send data to a PostgreSQL Database.
This Kamelet expects a JSON-formatted body. Use key:value pairs to map the JSON fields and parameters. For example, here is a query:
'INSERT INTO accounts (username,city) VALUES (:#username,:#city)'
Here is example input for the example query:
'{ "username":"oscerd", "city":"Rome"}'
59.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 name of the PostgreSQL Database. | string | ||
| password * | Password | The password to access a secured PostgreSQL Database. | string | ||
| query * | Query | The query to execute against the PostgreSQL Database. | string | INSERT INTO accounts (username,city) VALUES (:#username,:#city) | |
| serverName * | Server Name | The server name for the data source. | string | localhost | |
| username * | Username | The username to access a secured PostgreSQL Database. | string | ||
| serverPort | Server Port | The server port for the data source. | string | 5432 |
* = Fields marked with an asterisk are mandatory.
59.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
59.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
59.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
59.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
59.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
59.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
59.3.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the postgresql-sink Kamelet as a Knative sink by binding it to a Knative object.
postgresql-sink-binding.yaml
59.3.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the postgresql-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
postgresql-sink-binding.yaml
59.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 60. Predicate Filter Action 링크 복사링크가 클립보드에 복사되었습니다!
Filter based on a JSONPath Expression. Since this is a filter, the expression is a negation. This means that if the foo field of the example is equal to John, the message goes ahead. Otherwise it is filtered out.
60.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 is a negation. This means that if the | string | @.foo =~ /.*John/ |
* = Fields marked with an asterisk are mandatory.
60.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
60.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
60.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
60.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
60.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
60.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
60.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the predicate-filter-action Kamelet as an intermediate step in a Knative binding.
predicate-filter-action-binding.yaml
60.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the predicate-filter-action Kamelet as an intermediate step in a Kafka binding.
predicate-filter-action-binding.yaml
60.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 61. Protobuf Deserialize Action 링크 복사링크가 클립보드에 복사되었습니다!
Deserialize payload to Protobuf.
61.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) | string | message Person { required string first = 1; required string last = 2; } |
* = Fields marked with an asterisk are mandatory.
61.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
61.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
61.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
61.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
61.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
61.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
61.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the protobuf-deserialize-action Kamelet as an intermediate step in a Knative binding.
protobuf-deserialize-action-binding.yaml
61.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the protobuf-deserialize-action Kamelet as an intermediate step in a Kafka binding.
protobuf-deserialize-action-binding.yaml
61.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 62. Protobuf Serialize Action 링크 복사링크가 클립보드에 복사되었습니다!
Serialize payload to Protobuf.
62.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) | string | message Person { required string first = 1; required string last = 2; } |
* = Fields marked with an asterisk are mandatory.
62.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
62.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
62.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
62.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
62.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
62.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
62.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the protobuf-serialize-action Kamelet as an intermediate step in a Knative binding.
protobuf-serialize-action-binding.yaml
62.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the protobuf-serialize-action Kamelet as an intermediate step in a Kafka binding.
protobuf-serialize-action-binding.yaml
62.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 63. Regex Router Action 링크 복사링크가 클립보드에 복사되었습니다!
Update the destination using the configured regular expression and replacement string.
63.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 | string | ||
| replacement * | Replacement | Replacement when matching | string |
* = Fields marked with an asterisk are mandatory.
63.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
63.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
63.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
63.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
63.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
63.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
63.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the regex-router-action Kamelet as an intermediate step in a Knative binding.
regex-router-action-binding.yaml
63.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the regex-router-action Kamelet as an intermediate step in a Kafka binding.
regex-router-action-binding.yaml
63.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 64. 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 are included in the resulting message.
The optional parameter disabled represents the fields to exclude. If specified, the listed fields are excluded from the resulting message. This takes precedence over the enabled parameter.
The default value of enabled parameter is all, so all the fields in the payload are included.
The default value of disabled parameter is none, so no fields in the payload are excluded.
64.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 | string | foo:bar,c1:c2 | |
| 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.
64.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
64.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
64.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
64.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
64.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
64.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
64.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the replace-field-action Kamelet as an intermediate step in a Knative binding.
replace-field-action-binding.yaml
64.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the replace-field-action Kamelet as an intermediate step in a Kafka binding.
replace-field-action-binding.yaml
64.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 65. Salesforce Source 링크 복사링크가 클립보드에 복사되었습니다!
Receive updates from Salesforce.
65.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. | string | ||
| clientSecret * | Consumer Secret | The Salesforce application consumer secret. | string | ||
| password * | Password | The Salesforce user password. | string | ||
| query * | Query | The query to execute on Salesforce. | string | SELECT Id, Name, Email, Phone FROM Contact | |
| topicName * | Topic Name | The name of the topic or channel. | string | ContactTopic | |
| userName * | Username | The Salesforce username. | string | ||
| loginUrl | Login URL | The Salesforce instance login URL. | string | ||
| notifyForFields | Notify For Fields | Notify for fields. | string | ALL | |
| notifyForOperationCreate | Notify Operation Create | Notify for create operation. | boolean | True | |
| notifyForOperationDelete | Notify Operation Delete | Notify for delete operation. | boolean | False | |
| notifyForOperationUndelete | Notify Operation Undelete | Notify for undelete operation. | boolean | False | |
| notifyForOperationUpdate | Notify Operation Update | Notify for update operation. | boolean | False | |
| operation | Operation | The operation to use | string | subscribe | |
| rawPayload | Raw Payload | Use raw payload String for request and response (either JSON or XML depending on format), instead of DTOs, false by default. | boolean | False | |
| replayId | Replay Id | The replayId value to use when subscribing to the Streaming API. | long |
* = Fields marked with an asterisk are mandatory.
65.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
65.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
65.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
65.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
65.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
65.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
65.3.2. Knative Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the salesforce-source Kamelet as a Knative source by binding it to a Knative object.
salesforce-source-binding.yaml
65.3.3. Kafka Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the salesforce-source Kamelet as a Kafka source by binding it to a Kafka topic.
salesforce-source-binding.yaml
65.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 66. Salesforce Create Sink 링크 복사링크가 클립보드에 복사되었습니다!
Create an object in Salesforce.
The body of the message must contain the JSON of the Salesforce object, for example: { "Phone": "555", "Name": "Antonia", "LastName": "Garcia" }.
66.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. | string | ||
| clientSecret * | Consumer Secret | The Salesforce application consumer secret. | string | ||
| password * | Password | The Salesforce user password. | string | ||
| userName * | Username | The Salesforce username. | string | ||
| loginUrl | Login URL | The Salesforce instance login URL. | string | ||
| sObjectName | Object Name | The type of the object. | string | Contact |
* = Fields marked with an asterisk are mandatory.
66.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
66.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
66.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
66.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 67. Salesforce Delete Sink 링크 복사링크가 클립보드에 복사되었습니다!
Remove an object from Salesforce.
The data body must be JSON-formatted and it must contain two keys: sObjectId and sObjectName. For example: { "sObjectId": "XXXXX0", "sObjectName": "Contact" }
67.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. | string | ||
| clientSecret * | Consumer Secret | The Salesforce application consumer secret. | string | ||
| password * | Password | The Salesforce user password. | string | ||
| userName * | Username | The Salesforce username. | string | ||
| loginUrl | Login URL | The Salesforce instance login URL. | string |
* = Fields marked with an asterisk are mandatory.
67.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
67.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
67.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
67.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 68. 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" }
68.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. | string | ||
| clientSecret * | Consumer Secret | The Salesforce application consumer secret. | string | ||
| password * | Password | The Salesforce user password. | string | ||
| userName * | Username | The Salesforce username. | string | ||
| loginUrl | Login URL | The Salesforce instance login URL. | string |
* = Fields marked with an asterisk are mandatory.
68.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
68.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
68.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
68.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 69. SFTP Sink 링크 복사링크가 클립보드에 복사되었습니다!
Send data to an SFTP Server.
In the header, you can set the file / ce-file property to specify the filename to upload.
If you do not set the property in the header, the Kamelet uses the exchange ID for the filename.
69.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 FTP server. | string | ||
| connectionPort * | Connection Port | The port of the FTP server. | string | 22 | |
| directoryName * | Directory Name | The starting directory. | string | ||
| autoCreate | Autocreate Missing Directories | Automatically create the directory the files should be written to. | boolean | True | |
| binary | Binary | Specifies the file transfer mode, BINARY or ASCII. Default is ASCII (false). | boolean | False | |
| fileExist | File Existence | How to behave in case of file already existent. | string | Override | |
| passiveMode | Passive Mode | Specifies to use passive mode connection. | boolean | False | |
| password | Password | The password to access the FTP server. | string | ||
| privateKeyFile | Private Key File | Set the private key file so that the SFTP endpoint can do private key verification. | string | ||
| privateKeyPassphrase | Private Key Passphrase | Set the private key file passphrase so that the SFTP endpoint can do private key verification. | string | ||
| privateKeyUri | Private Key URI | Set the private key file (loaded from classpath by default) so that the SFTP endpoint can do private key verification. | string | ||
| strictHostKeyChecking | Strict Host Checking | Sets whether to use strict host key checking. | string | False | |
| 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. | boolean | True | |
| username | Username | The username to access the FTP server. | string |
* = Fields marked with an asterisk are mandatory.
69.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
69.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
69.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
69.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
69.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
69.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
69.3.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the sftp-sink Kamelet as a Knative sink by binding it to a Knative object.
sftp-sink-binding.yaml
69.3.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the sftp-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
sftp-sink-binding.yaml
69.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 70. SFTP Source 링크 복사링크가 클립보드에 복사되었습니다!
Receive data from an SFTP server.
70.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. | string | ||
| connectionPort * | Connection Port | The port of the FTP server. | string | 22 | |
| directoryName * | Directory Name | The starting directory. | string | ||
| autoCreate | Autocreate Missing Directories | Automatically create starting directory. | boolean | True | |
| binary | Binary | Specifies the file transfer mode, BINARY or ASCII. Default is ASCII (false). | boolean | False | |
| delete | Delete | If true, the file is deleted after it is processed successfully. | boolean | False | |
| idempotent | Idempotency | Skip already-processed files. | boolean | True | |
| 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. | boolean | False | |
| passiveMode | Passive Mode | Sets the passive mode connection. | boolean | False | |
| password | Password | The password to access the SFTP server. | string | ||
| privateKeyFile | Private Key File | Set the private key file so that the SFTP endpoint can do private key verification. | string | ||
| privateKeyPassphrase | Private Key Passphrase | Set the private key file passphrase so that the SFTP endpoint can do private key verification. | string | ||
| privateKeyUri | Private Key URI | Set the private key file (loaded from classpath by default) so that the SFTP endpoint can do private key verification. | string | ||
| recursive | Recursive | If a directory, look for files in all sub-directories as well. | boolean | False | |
| strictHostKeyChecking | Strict Host Checking | Sets whether to use strict host key checking. | string | False | |
| 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. | boolean | True | |
| username | Username | The username to access the SFTP server. | string |
* = Fields marked with an asterisk are mandatory.
70.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
70.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
70.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
70.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
70.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
70.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
70.3.2. Knative Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the sftp-source Kamelet as a Knative source by binding it to a Knative object.
sftp-source-binding.yaml
70.3.3. Kafka Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the sftp-source Kamelet as a Kafka source by binding it to a Kafka topic.
sftp-source-binding.yaml
70.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 71. Simple Filter Action 링크 복사링크가 클립보드에 복사되었습니다!
Filter based on simple expression.
71.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 | A simple expression to apply on the exchange to filter out some exchange | string |
* = Fields marked with an asterisk are mandatory.
71.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
71.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
71.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
71.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
71.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
71.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
71.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 72. Slack Source 링크 복사링크가 클립보드에 복사되었습니다!
Receive messages from a Slack channel.
72.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. | string | #myroom | |
| token * | Token |
The Bot User OAuth Access Token to access Slack. A Slack app that has the following permissions is required: | string | ||
| delay | Delay | The delay between polls. If no unit provided, milliseconds is the default. | string | 60000 | 60s or 6000 or 1m |
| naturalOrder | Natural Order | Create exchanges in natural order (oldest to newest) or not. | boolean | False | |
| serverUrl | Server URL | The Slack API server endpoint URL. | string |
* = Fields marked with an asterisk are mandatory.
72.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
72.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
72.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
72.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
72.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
72.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
72.3.2. Knative Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the slack-source Kamelet as a Knative source by binding it to a Knative object.
slack-source-binding.yaml
72.3.3. Kafka Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the slack-source Kamelet as a Kafka source by binding it to a Kafka topic.
slack-source-binding.yaml
72.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 73. Splunk Sink 링크 복사링크가 클립보드에 복사되었습니다!
Send data to Splunk either by using "submit" or "stream" mode.
The payload MUST be in json format.
73.1. Configuration Options 링크 복사링크가 클립보드에 복사되었습니다!
The following table summarizes the configuration options available for the splunk-sink Kamelet:
| Property | Name | Description | Type | Default | Example |
|---|---|---|---|---|---|
| password * | Password | The password to authenticate to Splunk Server. | string | ||
| serverHostname * | Splunk Server Address | The address of your Splunk server. | string | my_server_splunk.com | |
| username * | Username | The username to authenticate to Splunk Server. | string | ||
| app | Splunk App | The app name in Splunk. | string | ||
| connectionTimeout | Connection Timeout | Timeout in milliseconds when connecting to Splunk server | integer | 5000 | |
| index | Index | Splunk index to write to. | string | ||
| mode | Mode | The mode to publish events to Splunk. | string | stream | |
| protocol | Protocol | Connection Protocol to Splunk server. | string | https | |
| serverPort | Splunk Server Port | The address of your Splunk server. | integer | 8089 | |
| source | Source | The source named field of the data. | string | ||
| sourceType | Source Type | The source named field of the data. | string |
* = Fields marked with an asterisk are mandatory.
73.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
73.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
73.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
73.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
73.3.1.1. Prerequisites for Jbang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
Install
camelas a JBang command by running:jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
For example, you have a file named route.yaml with this content.
You can run it directly through the following command.
camel run route.yaml
camel run route.yaml
73.3.2. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the splunk-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
splunk-sink-binding.yaml
73.3.3. Prerequisites for Kafka 링크 복사링크가 클립보드에 복사되었습니다!
- Install Strimzi.
-
You must create a topic named
my-topicin the current namespace.
73.3.3.1. Procedure for using the cluster CLI with Kafka 링크 복사링크가 클립보드에 복사되었습니다!
-
Save the
splunk-sink-binding.yamlfile to your local drive, and then edit it as needed for your configuration. Run the sink with the following command:
kubectl apply -f splunk-sink-binding.yaml
kubectl apply -f splunk-sink-binding.yamlCopy to Clipboard Copied! Toggle word wrap Toggle overflow
73.3.3.2. Procedure for using the Kamel CLI with Kafka 링크 복사링크가 클립보드에 복사되었습니다!
Configure and run the sink with the following command.
kamel bind splunk-sink -p "sink.password=The Password" -p "sink.serverHostname=my_server_splunk.com" -p "sink.username=The Username" kafka.strimzi.io/v1beta1:KafkaTopic:my-topic
kamel bind splunk-sink -p "sink.password=The Password" -p "sink.serverHostname=my_server_splunk.com" -p "sink.username=The Username" kafka.strimzi.io/v1beta1:KafkaTopic:my-topic
This command creates the Pipe in the current namespace on the cluster.
73.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 74. Splunk Source 링크 복사링크가 클립보드에 복사되었습니다!
Retrieve data from Splunk and outputs in json format.
For the fields accepting time specifiers like earliestTime, Splunk accepts a wide variety of formats, please check Splunk documentation for more information.
74.1. Configuration Options 링크 복사링크가 클립보드에 복사되었습니다!
The following table summarizes the configuration options available for the splunk-source Kamelet:
| Property | Name | Description | Type | Default | Example |
|---|---|---|---|---|---|
| initEarliestTime * | Init Earliest Time | Initial start offset of the first search. | string | 05/17/22 08:35:46:456 | |
| password * | Password | The password to authenticate to Splunk Server. | string | ||
| query * | Query | The Splunk query to run. | string | ||
| serverHostname * | Splunk Server Address | The address of your Splunk server. | string | my_server_splunk.com | |
| username * | Username | The username to authenticate to Splunk Server. | string | ||
| app | Splunk App | The app name in Splunk. | string | ||
| connectionTimeout | Connection Timeout | Timeout in milliseconds when connecting to Splunk server | integer | ||
| count | Count | The maximum number of entities to return. | integer | ||
| delay | Delay | The number of milliseconds before the next poll. | integer | ||
| earliestTime | Earliest Time | Earliest time of the search time window. | string | 05/17/22 08:35:46:456 | |
| index | Index | Splunk index to write to. | string | ||
| latestTime | Latest Time | Latest time of the search time window. | string | 05/17/22 08:35:46:456 | |
| protocol | Protocol | Connection Protocol to Splunk server. | string | https | |
| repeat | Repeat | The maximum number of fires. | integer | ||
| serverPort | Splunk Server Port | The address of your Splunk server. | integer | 8089 | |
| source | Source | The source named field of the data. | string | ||
| sourceType | Source Type | The source named field of the data. | string |
* = Fields marked with an asterisk are mandatory.
74.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
74.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
74.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
74.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
74.3.1.1. Prerequisites for Jbang 링크 복사링크가 클립보드에 복사되었습니다!
- You must have installed JBang.
- You must have executed the following command.
jbang app install camel@apache/camel
jbang app install camel@apache/camel
For example, you have a file named route.yaml with this content.
You can now run it directly through the following command
camel run route.yaml
camel run route.yaml
74.3.2. Knative Source 링크 복사링크가 클립보드에 복사되었습니다!
You must use the splunk-source Kamelet as a Knative source by binding it to a Knative object.
splunk-source-binding.yaml
74.3.3. Kafka Source 링크 복사링크가 클립보드에 복사되었습니다!
You must use the splunk-source Kamelet as a Kafka source by binding it to a Kafka topic.
splunk-source-binding.yaml
74.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 75. Microsoft SQL Server Sink 링크 복사링크가 클립보드에 복사되었습니다!
Send data to a Microsoft SQL Server Database.
In your Pipe file, you must explicitly declare the SQL Server driver dependency in spec→integration→dependencies:
- "mvn:com.microsoft.sqlserver:mssql-jdbc:<version>"
This Kamelet expects a JSON-formatted body. Use key:value pairs to map the JSON fields and parameters. For example, here is a query:
'INSERT INTO accounts (username,city) VALUES (:#username,:#city)'
Here is example input for the example query:
'{ "username":"oscerd", "city":"Rome"}'
75.1. Configuration Options 링크 복사링크가 클립보드에 복사되었습니다!
The following table summarizes the configuration options available for the sqlserver-sink Kamelet:
| Property | Name | Description | Type | Default | Example |
|---|---|---|---|---|---|
| databaseName * | Database Name | The name of the SQL Server Database. | string | ||
| password * | Password | The password to access a secured SQL Server Database. | string | ||
| query * | Query | The query to execute against the SQL Server Database. | string | INSERT INTO accounts (username,city) VALUES (:#username,:#city) | |
| serverName * | Server Name | The server name for the data source. | string | localhost | |
| username * | Username | The username to access a secured SQL Server Database. | string | ||
| encrypt | Encrypt Connection | Encrypt the connection to SQL Server. | boolean | False | |
| serverPort | Server Port | The server port for the data source. | string | 1433 | |
| trustServerCertificate | Trust Server Certificate | Trust Server Certificate | boolean | True |
* = Fields marked with an asterisk are mandatory.
75.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
75.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
75.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
75.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
75.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
75.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
75.3.2. Knative Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the sqlserver-sink Kamelet as a Knative sink by binding it to a Knative object.
sqlserver-sink-binding.yaml
75.3.3. Kafka Sink 링크 복사링크가 클립보드에 복사되었습니다!
You can use the sqlserver-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
sqlserver-sink-binding.yaml
75.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 76. Telegram Source 링크 복사링크가 클립보드에 복사되었습니다!
Receive all messages that people send to your Telegram bot.
To create a bot, contact the @botfather account by using the Telegram app.
The source attaches the following header to the messages:
-
chat-id/ce-chatid: The ID of the chat where the message comes from.
76.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 can obtain it from the Telegram @botfather. | string |
* = Fields marked with an asterisk are mandatory.
76.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
76.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
76.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
76.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
76.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
76.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
76.3.2. Knative Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the telegram-source Kamelet as a Knative source by binding it to a Knative object.
telegram-source-binding.yaml
76.3.3. Kafka Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the telegram-source Kamelet as a Kafka source by binding it to a Kafka topic.
telegram-source-binding.yaml
76.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 77. Throttle Action 링크 복사링크가 클립보드에 복사되었습니다!
The Throttle action allows you to ensure that a specific sink does not get overloaded.
77.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 | 10 | |
| timePeriod | Time Period | Sets the time period during which the maximum request count is valid for, in milliseconds | string | 1000 |
* = Fields marked with an asterisk are mandatory.
77.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
77.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
77.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
77.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
77.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
77.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
77.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the throttle-action Kamelet as an intermediate step in a Knative binding.
throttle-action-binding.yaml
77.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the throttle-action Kamelet as an intermediate step in a Kafka binding.
throttle-action-binding.yaml
77.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 78. Timer Source 링크 복사링크가 클립보드에 복사되었습니다!
Produces periodic messages with a custom payload.
78.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. | string | hello world | |
| contentType | Content Type | The content type of the generated message. | string | text/plain | |
| period | Period | The interval (in milliseconds) to wait between producing the next message. | integer | 1000 | |
| repeatCount | Repeat Count | Specifies a maximum limit of number of fires | integer |
* = Fields marked with an asterisk are mandatory.
78.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
78.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
78.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
78.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
78.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
78.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
78.3.2. Knative Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the timer-source Kamelet as a Knative source by binding it to a Knative object.
timer-source-binding.yaml
78.3.3. Kafka Source 링크 복사링크가 클립보드에 복사되었습니다!
You can use the timer-source Kamelet as a Kafka source by binding it to a Kafka topic.
timer-source-binding.yaml
78.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 79. Timestamp Router Action 링크 복사링크가 클립보드에 복사되었습니다!
Update the topic field as a function of the original topic name and the record timestamp.
79.1. Configuration Options 링크 복사링크가 클립보드에 복사되었습니다!
The following table summarizes the configuration options available for the timestamp-router-action Kamelet:
| Property | Name | Description | Type | Default | Example |
|---|---|---|---|---|---|
| topicFormat | Topic Format | Format string which can contain '$[topic]' and '$[timestamp]' as placeholders for the topic and timestamp, respectively. | string | topic-$[timestamp] | |
| timestampFormat | Timestamp Format | Format string for the timestamp that is compatible with java.text.SimpleDateFormat. | string | yyyyMMdd | |
| timestampHeaderName | Timestamp Header Name | The name of the header containing a timestamp | string | kafka.TIMESTAMP |
* = Fields marked with an asterisk are mandatory.
79.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
79.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
79.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
79.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
79.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
79.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
79.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the timestamp-router-action Kamelet as an intermediate step in a Knative binding.
timestamp-router-action-binding.yaml
79.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the timestamp-router-action Kamelet as an intermediate step in a Kafka binding.
timestamp-router-action-binding.yaml
79.4. Kamelets source file 링크 복사링크가 클립보드에 복사되었습니다!
Chapter 80. Value to Key Action 링크 복사링크가 클립보드에 복사되었습니다!
Replace the Kafka record key with a new key formed from a fields subset coming from the message body.
80.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. | string |
* = Fields marked with an asterisk are mandatory.
80.2. Dependencies 링크 복사링크가 클립보드에 복사되었습니다!
80.2.1. Quarkus dependencies 링크 복사링크가 클립보드에 복사되었습니다!
80.3. Usage 링크 복사링크가 클립보드에 복사되었습니다!
80.3.1. Camel JBang usage 링크 복사링크가 클립보드에 복사되었습니다!
80.3.1.1. Prerequisites for JBang 링크 복사링크가 클립보드에 복사되었습니다!
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
jbang app install camel@apache/camelCopy to Clipboard Copied! Toggle word wrap Toggle overflow
80.3.1.2. Running a route with JBang 링크 복사링크가 클립보드에 복사되었습니다!
Suppose you have a file named route.yaml with this content:
You can now run it directly through the following command.
camel run route.yaml
camel run route.yaml
80.3.2. Knative Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the value-to-key-action Kamelet as an intermediate step in a Knative binding.
value-to-key-action-binding.yaml
80.3.3. Kafka Action 링크 복사링크가 클립보드에 복사되었습니다!
You can use the value-to-key-action Kamelet as an intermediate step in a Kafka binding.
value-to-key-action-binding.yaml