Return-Path: X-Original-To: apmail-camel-commits-archive@www.apache.org Delivered-To: apmail-camel-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A4475181CB for ; Thu, 24 Dec 2015 18:19:08 +0000 (UTC) Received: (qmail 52083 invoked by uid 500); 24 Dec 2015 18:19:08 -0000 Delivered-To: apmail-camel-commits-archive@camel.apache.org Received: (qmail 52030 invoked by uid 500); 24 Dec 2015 18:19:08 -0000 Mailing-List: contact commits-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list commits@camel.apache.org Received: (qmail 52021 invoked by uid 99); 24 Dec 2015 18:19:08 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Dec 2015 18:19:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id F0B39180455 for ; Thu, 24 Dec 2015 18:19:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.247 X-Spam-Level: * X-Spam-Status: No, score=1.247 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-0.554, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id jP7Xk9L0_Cvs for ; Thu, 24 Dec 2015 18:18:56 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTP id 42F8B20D57 for ; Thu, 24 Dec 2015 18:18:56 +0000 (UTC) Received: from svn01-us-west.apache.org (svn.apache.org [10.41.0.6]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 7B5A7E0428 for ; Thu, 24 Dec 2015 18:18:55 +0000 (UTC) Received: from svn01-us-west.apache.org (localhost [127.0.0.1]) by svn01-us-west.apache.org (ASF Mail Server at svn01-us-west.apache.org) with ESMTP id 172903A0296 for ; Thu, 24 Dec 2015 18:18:55 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r976305 - in /websites/production/camel/content: cache/main.pageCache ignite.html Date: Thu, 24 Dec 2015 18:18:54 -0000 To: commits@camel.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20151224181855.172903A0296@svn01-us-west.apache.org> Author: buildbot Date: Thu Dec 24 18:18:54 2015 New Revision: 976305 Log: Production update by buildbot for camel Modified: websites/production/camel/content/cache/main.pageCache websites/production/camel/content/ignite.html Modified: websites/production/camel/content/cache/main.pageCache ============================================================================== Binary files - no diff available. Modified: websites/production/camel/content/ignite.html ============================================================================== --- websites/production/camel/content/ignite.html (original) +++ websites/production/camel/content/ignite.html Thu Dec 24 18:18:54 2015 @@ -92,20 +92,20 @@ <version>${camel.version}</version> <!-- use the same version as your Camel core version --> </dependency> ]]> -

URI formats and options

Ignite Cache endpoint


This endpoint allows you to interact with an Ignite Cache:

+

URI formats and options

Ignite Cache endpoint

This endpoint allows you to interact with an Ignite Cache:

-

Offers both a Producer (to invoke cache operations on an Ignite cache) and a Consumer (to consume changes from a continuous query).

Options

OptionTypeDefault valueDescriptionCompulsoryConsumer/producer
operationIgniteCacheOperation enum---

Cache operation to perform.

Possible values: GET, PUT, REMOVE, SIZE, REBALANCE, QUERY, CLEAR.

NProducer
failIfInexistentCachebooleanfalseWhether to fail the initialization if the cache doesn't exist.NProducer
cachePeekModeCachePeekMode (Ignite) enumALLThe cache peek mode used for SIZE operations.NProducer
queryQuery---

The query used for QUERY operations (as a producer) or to launch the continuous query (as a consumer).

You can use a reference to a registry bean with a syntax like: ?query=#myQuery.

Y for the consumer

N for the producer

Producer (for QUERY operation) and Consumer
remoteFilterCacheEntryEventSerializableFil ter

---

An optional remote filter for the continuous query consumer.

You can use a reference to a registry bean with a syntax like: ?remoteFilter=#myRemoteFilter.

NConsumer
oneExchangePerUpdatebooleantrueWhether to send one exchange per cache update, even if multiple changes arrive in a group.NConsumer
fireExistingQueryResultsbooleanfalseWhen starting the continuous query consumer, whether to fire existing cache results.NConsumer
autoUnsubscribeboolean

ContinuousQuery.DFLT_AUTO_UNSUBSCRIBE

Auto-unsubscribe flag on the Continuous Query (see Ignite docs).NConsumer
pageSizeint

ContinuousQuery.DFLT_PAGE_SIZE

Page size on the Continuous Query (see Ignite docs).NConsumer
timeIntervallong

ContinuousQuery.DFLT_TIME_INTER VAL

Time interval in millis on the Continuous Query (see Ignite docs).NConsumer

Ignite Compute endpoint


This endpoint allows you to run compute operations on the cluster by passing in an IgniteCallable, an IgniteRunnable, an IgniteClosure, or collections of them, along with their parameters if necessary. 

+

Offers both a Producer (to invoke cache operations on an Ignite cache) and a Consumer (to consume changes from a continuous query).

The cache value is always the body of the message, whereas the cache key is always stored in the IgniteConstants.IGNITE_CACHE_KEY message header.

Even if you configure a fixed operation in the endpoint URI, you can vary it per-exchange by setting the IgniteConstants.IGNITE_CACHE_OPERATION message header.

Options

OptionTypeDefault valueDescriptionCompulsoryConsum er/producer
operationIgniteCacheOperation enum---

Cache operation to perform.

Possible values: GET, PUT, REMOVE, SIZE, REBALANCE, QUERY, CLEAR.

NProducer
failIfInexistentCachebooleanfalseWhether to fail the initialization if the cache doesn't exist.NProducer
cachePeekModeCachePeekMode (Ignite) enumALLThe cache peek mode used for SIZE operations.NProducer
queryQuery---

The query used for QUERY operations (as a producer) or to launch the continuous query (as a consumer). You can use a reference to a registry bean with a syntax like: ?query=#myQuery.

Y for the consumer / N for the producer

Producer (for QUERY operation) and Consumer
remoteFilterCacheEntryEventSerializableFilter

---

An optional remote filter for the continuous query consumer. You can use a reference to a registry bean with a syntax like: ?remoteFilter=#myRemoteFilter.

NConsumer
oneExchangePerUpdatebooleantrueWhether to send one exchange per cac he update, even if multiple changes arrive in a group.NConsumer
fireExistingQueryResultsbooleanfalseWhen starting the continuous query consumer, whether to fire existing cache results.NConsumer
autoUnsubscribeboolean

ContinuousQuery.DFLT_AUTO_UNSUBSCRIBE

Auto-unsubscribe flag on the Continuous Query (see Ignite docs).NConsumer
pageSizeint

ContinuousQuery.DFLT_PAGE_SIZE

Page size on the Continuous Query (see Ignite docs).NConsumer
timeIntervallong

ContinuousQuery.DFLT_TIME_INTERVAL

Time interval in millis on the Continuous Query (see Ignite docs).NConsumer

Headers used

This endpoint uses the following headers:

Header nameConstantExpected typeDescription

CamelIgniteCacheKey

IgniteConstants.IGNITE_CACHE_KEYStringThe cache key for the entry value in the message body.
CamelIgniteCacheQueryIgniteConstants.IGNITE_CACHE_QUERYQueryThe query to run (producer) when invoking the QUERY operation.
CamelIgniteCacheOperationIgniteConstants.IGNITE_CACHE_OPERATIONIgniteCacheOperation enumAllows you to dynamically change the cache operation to execute (producer).
CamelIgniteCachePeekModeIgniteConstants.IGNITE_CACHE_PEEK_MODECachePeekMode enumAllows you to dynamically change the cache peek mode when running the SIZE operation.
CamelIgniteCacheEventTypeIgniteConstants.IGNITE_CACHE_EVENT_TYPEint (EventType constants)This header carries the received event type when using the continuous query consumer.
CamelIgniteCacheNameIgniteConstants.IGNITE_CACHE_NAMEString

This header carries the cache name for which a continuous query event was received (consumer).

It does not allow you to dynamically change the cache against which a producer operation is performed. Use EIPs for that (e.g. recipient list, dynamic router).

CamelIgniteCacheOldValueIgniteConstants.IGNITE_CACHE_OLD_VALUEObjectThis header carries the old cache value when passed in the incoming cache event (consumer).

Ignite Compute endpoint

This endpoint allows you to run compute operations on the cluster by passing in an IgniteCallable, an IgniteRunnable, an IgniteClosure, or collections of them, along with their parameters if necessary. 

-

This endpoint only supports producers.

Options

taskName

OptionTypeDefault valueDescriptionCompulsoryConsumer/producer

executionType

IgniteComputeExecutionType enum

---

The compute operation to perform.

Possible values: CALL, BRO ADCAST, APPLY, EXECUTE, RUN, AFFINITY_CALL, AFFINITY_RUN.

YProducer

clusterGroupExpression

ClusterGroupExpression
---

An expression that returns the Cluster Group for the IgniteCompute instance.

NProducer
String
---The task name, only used when performing the EXECUTE if a ComputeTask is not passed in the payload.NProducer

computeName

String
---

The name for the IgniteCompute instances produced by this endpoint.

N

Producer

timeoutMillis

Long

---

The timeout for the compute job.

NProducer

Headers used

Header nameConstantExpected typeDescription

CamelIgniteComputeExecutionType

IgniteConstants.IGNITE_COMPUTE_EXECUTION_TYPEIgniteComputeExecutionType enumAllows you to dynamically change the compute operation to perform.

CamelIgniteComputeParameters 

IgniteConstants.IGNITE_COMPUTE_PARAMSAny object or Collection of objects.Parameters for APPLY, BROADCAST and EXECUTE operations.

CamelIgniteComputeReducer

IgniteConstants.IGNIT E_COMPUTE_REDUCERIgniteReducerReducer for the APPLY and CALL operations.
CamelIgniteComputeAffinityCacheNameIgniteConstants.IGNITE_COMPUTE_AFFINITY_CACHE_NAMEStringAffinity cache name for the AFFINITY_CALL and AFFINITY_RUN operations.

CamelIgniteComputeAffinityKey

IgniteConstants.IGNITE_COMPUTE_AFFINITY_KEYObjectAffinity key for the AFFINITY_CALL and AFFINITY_RUN operations.

Expected payload types

OperationExpected payloads
CALL
Collection of IgniteCallable, or a single IgniteCallable.
BROADCAST
IgniteCallable, IgniteRunnable, IgniteClosure.
APPLY
IgniteClosure.
EXECUTE
ComputeTask, Class<? extends ComputeTask> or an object representing parameters if the taskName option is not null.
RUN
A Collection of IgniteRunnables, or a single IgniteRunnable.
AFFINITY_CALL
IgniteCallable.
AFFINITY_RUN
IgniteRunnable.

Ignite Messaging endpoint

 The Ignite Messaging endpoint allows you to send and consume messages from an Ignite topic.

+

This endpoint only supports producers.

The host part of the endpoint URI is a symbolic endpoint ID, it is not used for any purposes. The endpoint tries to run the object passed in the body of the IN message as the compute job. See below for expected payload types per operation.

Options

OptionTypeDefault valueDescriptionCompulsoryConsumer/producer

executionType

IgniteComputeExecutionType en um

---

The compute operation to perform. Possible values: CALL, BROADCAST, APPLY, EXECUTE, RUN, AFFINITY_CALL, AFFINITY_RUN.

YProducer

clusterGroupExpression

ClusterGroupExpression---

An expression that returns the Cluster Group for the IgniteCompute instance.

NProducer

taskName

String---The task name, only used when performing the EXECUTE if a ComputeTask is not passed in the payload.NProducer

computeName

String---

The name for the IgniteCompute instances produced by this endpoint.

N

Producer

timeoutMillis

Long

---

The timeout for the compute job.

NProducer

Headers used

This endpoint uses the following headers:

Header nameConstantExpected typeDescription

CamelIgniteComputeExecutionType

IgniteConstants.IGNITE_COMPUTE_EXECUTION_TYPEIgniteComputeExecutionType enumAllows you to dynamically change the compute operation to perform.

CamelIgniteComputeParameters 

IgniteConstants.IGNITE_COMPUTE_PARAMSAny object or Collection of objects.Parameters for APPLY, BROADCAST and EXECUTE operations.

CamelIgniteComputeReducer

IgniteConstants.IGNITE_COMPUTE_REDUCERIgniteReducerReducer for the APPLY and CALL operations.
CamelIgniteComputeAffinityCacheNameIgniteConstants.IGNITE_COMPUTE_AFFINITY_CACHE_NAMEStringAffinity cache name for the AFFINITY_CALL and AFFINITY_RUN operations.

CamelIgniteComputeAffinityKey

IgniteConstants.IGNITE_COMPUTE_AFFINITY_KEYObjectAffinity key for the AFFINITY_CALL and AFFINITY_RUN operations.
< h4 id="Ignite-Expectedpayloadtypes">Expected payload types

Each operation expects the indicated types:

OperationExpected payloads
CALL
Collection of IgniteCallable, or a single IgniteCallable.
BROADCAST
IgniteCallable, IgniteRunnable, IgniteClosure.
APPLY
IgniteClosure.
EXECUTE
ComputeTask, Class<? extends Com puteTask> or an object representing parameters if the taskName option is not null.
RUN
A Collection of IgniteRunnables, or a single IgniteRunnable.
AFFINITY_CALL
IgniteCallable.
AFFINITY_RUN
IgniteRunnable.

Ignite Messaging endpoint

 The Ignite Messaging endpoint allows you to send and consume messages from an Ignite topic.

-

This endpoint supports producers (to send messages) and consumers (to receive messages).

Options

OptionTypeDefault valueDescriptionCompulsoryConsumer/producer

clusterGroupExpression

ClusterGroupExpression
---

An expression that returns the Cluster Group for the IgniteMessag ing instance.

NConsumer and Producer

sendMode

IgniteMessagingSendMode enum

UNORDERED

The send mode to use.

Possible values: UNORDERED, ORDERED.

NProducer

timeout

Long

---

The timeout for the send operation when using ordered messages.

NProducer

Ignite Events endpoint

The Ignite Events endpoint allows you to receive events from the Ignite cluster by creating a local event listener.

+

This endpoint supports producers (to send messages) and consumers (to receive messages).

Options

OptionTypeDefault valueDescriptionCompulsoryConsumer/producer
clusterGroupExpression

ClusterGroupExpression

---

An expression that returns the Cluster Group for the IgniteMessaging insta nce.

NConsumer and Producer
sendMode

IgniteMessagingSendMode enum

UNORDERED

The send mode to use.

Possible values: UNORDERED, ORDERED.

NProducer
timeout

Long

---

The timeout for the send operation when using ordered messages.

NProducer

Headers used

This endpoint uses the following headers:

Header nameConstantExpected typeDescription

CamelIgniteMessagingTopic

IgniteConstants.IGNITE_MESSAGING_TOPICString

Allow s you to dynamically change the topic to send messages to (producer).
It also carries the topic on which a message was received (consumer).

CamelIgniteMessagingUUID

IgniteConstants.IGNITE_MESSAGING_UUIDUUIDThis header is filled in with the UUID of the subscription when a message arrives (consumer).

Ignite Events endpoint

The Ignite Events endpoint allows you to receive events from the Ignite cluster by creating a local event listener.

-

This endpoint only supports consumers.

The Exchanges created by this consumer put the received Event object into the body of the IN message.

Options

OptionTypeDefault valueDescriptionCompulsoryConsumer/producer

events

Set<Integer> or String
EventType.EVTS_ALL

The event IDs to subscribe to. You can set a Set<Integer> directly where the IDs are the different constants in org.apache.ignite.events.EventType, or you can specify a comma-separated list of constant names.

For example: EVT_CACHE_ENTRY_CREATED,EVT_CACHE_OBJECT_REMOVED,EVT_IGFS_DIR_CREATED.

NConsumer

clusterGroupExpression

ClusterGroupExpression
---

An expression that returns the Cluster Group to be used by the IgniteEvents instance.

NConsumer

Ignite Sets endpoint

The Ignite Sets endpoint allows you to interact with Ignite Set data structures.

+

This endpoint only supports consumers.

The Exchanges created by this consumer put the received Event object into the body of the IN message.

Options

OptionTypeDefault valueDescriptionCompulsoryConsumer/producer

events

Set<Integer> or String

EventType.EVTS_ALL

The event IDs to subscribe to. You can set a Set<Integer> directly where the IDs are the different constants in org.apache.ignite.events.EventType, or you can specify a comma-separated list of constant names.
For example: EVT_CACHE_ENTRY_CREATED,EVT_CACHE_OBJECT_REMOVED,EVT_IGFS_DIR_CREATED.

NConsumer

clusterGroupExpression

ClusterGroupExpression

---

An expression that returns the Cluster Group to be used by the IgniteEvents instance.

NConsumer

Ignite Sets endpoint

The Ignite Sets endpoint allows you to interact with Ignite Set data structures.

-

This endpoint only supports producers.

Options

OptionTypeDefault valueDescriptionCompulsoryConsumer/producer

operation

IgniteSetOperation enum

---

The operation to invoke on the Ignite Set.

Superseded by the IgniteConstants.IGNITE_SETS_OPERATIO N header in the IN message.

Possible values: CONTAINS, ADD, SIZE, REMOVE, ITERATOR, CLEAR, RETAIN_ALL, ARRAY.

NProducer

configuration

CollectionConfiguration
empty CollectionConfiguration

The configuration for this data structure. You can also specify inner properties by using the config. prefix.

For example: ?config.backups=4

NProducer

Ignite Queue endpoint

The Ignite Queue endpoint allows you to interact with Ignite Queue data structures.

+

This endpoint only supports producers.

Options

OptionTypeDefault valueDescriptionCompulsoryConsumer/producer

operation

IgniteSetOperation enum

---

The operation to invoke on the Ignite Set.
Superseded by the Ignit eConstants.IGNITE_SETS_OPERATION header in the IN message.
Possible values: CONTAINS, ADD, SIZE, REMOVE, ITERATOR, CLEAR, RETAIN_ALL, ARRAY.

NProducer

configuration

CollectionConfigurationempty CollectionConfiguration

The configuration for this data structure. You can also specify inner properties by using the config. prefix.

For example: ?config.backups=4

NProducer

Headers used

This endpoint uses the following headers:

Header nameConstantExpected typeDescription

CamelIgniteSetsOperation

IgniteConstants.IGNITE_SETS_OPERATIONIgniteSetOperation enum

Allows you to dynamically change the set operation.

Ignite Queue endpoint

The Ignite Queue endpoint allows you to interact with Ignite Queue data structures.

-

This endpoint only supports producers.

Options

OptionTypeDefault valueDescriptionCompulsoryConsumer/producer

operation

IgniteQueueOperation enum

---

The operation to invoke on the Ignite Queue.

Superseded by the IgniteConstants.IGNITE_QUEUE_OPE RATION header in the IN message.

Possible values: CONTAINS, ADD, SIZE, REMOVE, ITERATOR, CLEAR, RETAIN_ALL, ARRAY, DRAIN, ELEMENT, PEEK, OFFER, POLL, TAKE, PUT.

NProducer

configuration

CollectionConfiguration
empty CollectionConfiguration

The configuration for this data structure. You can also specify inner properties by using the config. prefix.

For example: ?config.backups=4

NProducer

Ignite ID Generator endpoint

The Ignite ID Generator endpoint allows you to interact with Ignite Atomic Sequences and ID Generators.

+

This endpoint only supports producers.

Options

OptionTypeDefault valueDescriptionCompulsoryConsumer/producer

operation

IgniteQueueOperation enum

---

The operation to invoke on the Ignite Queue.

Superseded by the IgniteConstants.IGNITE_QUEUE_OPE RATION header in the IN message.

Possible values: CONTAINS, ADD, SIZE, REMOVE, ITERATOR, CLEAR, RETAIN_ALL, ARRAY, DRAIN, ELEMENT, PEEK, OFFER, POLL, TAKE, PUT.

NProducer

configuration

CollectionConfiguration
empty CollectionConfiguration

The configuration for this data structure. You can also specify inner properties by using the config. prefix.

For example: ?config.backups=4

NProducer
timeoutMillisLong---The timeout in milliseconds to use when invoking the OFFER or POLL operations.NProducer
capacityint--- (unbounded)The queue capacity if you'd like to use a bounded queue.NProducer

Headers used

This endpoint uses the following headers:

< th colspan="1" rowspan="1" class="confluenceTh">Expected type
Header nameConstantDescription

CamelIgniteQueueOperation

IgniteConstants.IGNITE_QUEUE_OPERATIONIgniteQueueOperation enum

Allows you to dynamically change the queue operation.

CamelIgniteQueueMaxElementsIgniteConstants.IGNITE_QUEUE_MAX_ELEMENTSInteger or intWhen invoking the DRAIN operation, the amount of items to drain.
CamelIgniteQueueTransferredCountIgniteConstants.IGNITE_QUEUE_TRANSFERRED_COUNTInteger or intThe amount of items transferred as the result of the DRAIN operation.
CamelIgniteQueueTimeoutMillisIgniteConstants.IGNITE_QUEUE_TIMEOUT_MILLISLong or longDynamically sets the timeout in milliseconds to use when invoking the OFFER or POLL operations. 

Ignite ID Generator endpoint

The Ignite ID Generator endpoint allows you to interact with Ignite Atomic Sequences and ID Generators.

This endpoint only supports producers.

Options

OptionTypeDefault valueDescriptionCompulsoryConsumer/producer

operation

IgniteIdGenOperation enum

---

The operation to invoke on the Ignite ID Generator.

Superseded by the IgniteConstants.IGNITE_ID GEN_OPERATION header in the IN message.

Possible values: ADD_AND_GET, GET, GET_AND_ADD, GET_AND_INCREMENT, INCREMENT_AND_GET.

NProducer

configuration

CollectionConfiguration
empty CollectionConfiguration

The configuration for this data structure. You can also specify inner properties by using the config. prefix.

For example: ?c onfig.backups=4

NProducer

Initializing the Ignite component

Each instance of the Ignite component is associated with an underlying org.apache.ignite.Ignite instance. You can interact with two Ignite clusters by initializing two instances of the Ignite component and binding them to different IgniteConfigurations. There are 3 ways to initialize the Ignite component:

  • By passing in an existing org.apache.ignite.Ignite instance. Here's an example using Spring config:
-


Additionally, if using Camel programmatically, there are several convenience static methods in IgniteComponent that return a component out of any of these configuration options:

  • IgniteComponent#fromIgnite(Ignite)
  • IgniteComponent#fromConfiguration(IgniteConfiguration)
  • IgniteComponent#fromInputStream(InputStream)
  • IgniteComponent#fromUrl(URL)
  • IgniteComponent#fromLocation(String)

General options

All endpoints share the following options:

OptionTypeDefault valueDescripti on
propagateIncomingBodyIfNoReturnValuebooleantrueIf the underlying Ignite operation returns void (no return type), this flag determines whether the producer will copy the IN body into the OUT body.
treatCollectionsAsCacheObjectsbooleanfalseSome Ignite operations can deal with multiple elements at once, if passed a Collection. Enabling this option will treat Collections as a single object, invoking the operation variant for cardinality 1.

 

See Also

+


Additionally, if using Camel programmatically, there are several convenience static methods in IgniteComponent that return a component out of any of these configuration options:

  • IgniteComponent#fromIgnite(Ignite)
  • IgniteComponent#fromConfiguration(IgniteConfiguration)
  • IgniteComponent#fromInputStream(InputStream)
  • IgniteComponent#fromUrl(URL)
  • IgniteComponent#fromLocation(String)


You may use those methods to quickly create an IgniteComponent with your chosen configuration technique.

General options

All endpoints share the following options:

Option TypeDefault valueDescription
propagateIncomingBodyIfNoReturnValuebooleantrueIf the underlying Ignite operation returns void (no return type), this flag determines whether the producer will copy the IN body into the OUT body.
treatCollectionsAsCacheObjectsbooleanfalseSome Ignite operations can deal with multi ple elements at once, if passed a Collection. Enabling this option will treat Collections as a single object, invoking the operation variant for cardinality 1.

 

See Also