Ignite Cache
Perform cache operations on an Ignite cache or consume changes from a continuous query.
What’s inside
-
Ignite Cache component, URI syntax:
ignite-cache:cacheName -
Ignite Compute component, URI syntax:
ignite-compute:endpointId -
Ignite Events component, URI syntax:
ignite-events:endpointId -
Ignite ID Generator component, URI syntax:
ignite-idgen:name -
Ignite Messaging component, URI syntax:
ignite-messaging:topic -
Ignite Queues component, URI syntax:
ignite-queue:name -
Ignite Sets component, URI syntax:
ignite-set:name
Please refer to the above links for usage and configuration details.
Maven coordinates
<dependency>
<groupId>org.apache.camel.springboot</groupId>
<artifactId>camel-ignite-starter</artifactId>
</dependency>Spring Boot Auto-Configuration
The starter supports 37 options, which are listed below.
| Name | Description | Default | Type |
|---|---|---|---|
camel.component.ignite-cache.autowired-enabled | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean |
camel.component.ignite-cache.bridge-error-handler | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean |
camel.component.ignite-cache.enabled | Whether to enable auto configuration of the ignite-cache component. This is enabled by default. | Boolean | |
camel.component.ignite-cache.ignite | To use an existing Ignite instance. The option is a org.apache.ignite.Ignite type. | Ignite | |
camel.component.ignite-cache.ignite-configuration | Allows the user to set a programmatic ignite configuration. The option is a org.apache.ignite.configuration.IgniteConfiguration type. | IgniteConfiguration | |
camel.component.ignite-cache.lazy-start-producer | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | Boolean |
camel.component.ignite-compute.autowired-enabled | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean |
camel.component.ignite-compute.enabled | Whether to enable auto configuration of the ignite-compute component. This is enabled by default. | Boolean | |
camel.component.ignite-compute.ignite | To use an existing Ignite instance. The option is a org.apache.ignite.Ignite type. | Ignite | |
camel.component.ignite-compute.ignite-configuration | Allows the user to set a programmatic ignite configuration. The option is a org.apache.ignite.configuration.IgniteConfiguration type. | IgniteConfiguration | |
camel.component.ignite-compute.lazy-start-producer | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | Boolean |
camel.component.ignite-events.autowired-enabled | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean |
camel.component.ignite-events.bridge-error-handler | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean |
camel.component.ignite-events.enabled | Whether to enable auto configuration of the ignite-events component. This is enabled by default. | Boolean | |
camel.component.ignite-events.ignite | To use an existing Ignite instance. The option is a org.apache.ignite.Ignite type. | Ignite | |
camel.component.ignite-events.ignite-configuration | Allows the user to set a programmatic ignite configuration. The option is a org.apache.ignite.configuration.IgniteConfiguration type. | IgniteConfiguration | |
camel.component.ignite-idgen.autowired-enabled | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean |
camel.component.ignite-idgen.enabled | Whether to enable auto configuration of the ignite-idgen component. This is enabled by default. | Boolean | |
camel.component.ignite-idgen.ignite | To use an existing Ignite instance. The option is a org.apache.ignite.Ignite type. | Ignite | |
camel.component.ignite-idgen.ignite-configuration | Allows the user to set a programmatic ignite configuration. The option is a org.apache.ignite.configuration.IgniteConfiguration type. | IgniteConfiguration | |
camel.component.ignite-idgen.lazy-start-producer | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | Boolean |
camel.component.ignite-messaging.autowired-enabled | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean |
camel.component.ignite-messaging.bridge-error-handler | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean |
camel.component.ignite-messaging.enabled | Whether to enable auto configuration of the ignite-messaging component. This is enabled by default. | Boolean | |
camel.component.ignite-messaging.ignite | To use an existing Ignite instance. The option is a org.apache.ignite.Ignite type. | Ignite | |
camel.component.ignite-messaging.ignite-configuration | Allows the user to set a programmatic ignite configuration. The option is a org.apache.ignite.configuration.IgniteConfiguration type. | IgniteConfiguration | |
camel.component.ignite-messaging.lazy-start-producer | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | Boolean |
camel.component.ignite-queue.autowired-enabled | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean |
camel.component.ignite-queue.enabled | Whether to enable auto configuration of the ignite-queue component. This is enabled by default. | Boolean | |
camel.component.ignite-queue.ignite | To use an existing Ignite instance. The option is a org.apache.ignite.Ignite type. | Ignite | |
camel.component.ignite-queue.ignite-configuration | Allows the user to set a programmatic ignite configuration. The option is a org.apache.ignite.configuration.IgniteConfiguration type. | IgniteConfiguration | |
camel.component.ignite-queue.lazy-start-producer | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | Boolean |
camel.component.ignite-set.autowired-enabled | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean |
camel.component.ignite-set.enabled | Whether to enable auto configuration of the ignite-set component. This is enabled by default. | Boolean | |
camel.component.ignite-set.ignite | To use an existing Ignite instance. The option is a org.apache.ignite.Ignite type. | Ignite | |
camel.component.ignite-set.ignite-configuration | Allows the user to set a programmatic ignite configuration. The option is a org.apache.ignite.configuration.IgniteConfiguration type. | IgniteConfiguration | |
camel.component.ignite-set.lazy-start-producer | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | Boolean |