Apache Ignite 1 is no longer supported
Please consider using one the following alternatives: No alternative components suggested.
Get the byte array from Ignite Cache and adds it as the content of a FlowFile.The processor uses the value of FlowFile attribute (Ignite cache entry key) as the cache key lookup. If the entry corresponding to the key is not found in the cache an error message is associated with the FlowFile Note - The Ignite Kernel periodically outputs node performance statistics to the logs. This message can be turned off by setting the log level for logger 'org.apache.ignite' to WARN in the logback.xml configuration file.
Ignite, get, read, cache, key
In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values, and whether a property supports the NiFi Expression Language.
| Display Name | API Name | Default Value | Allowable Values | Description |
|---|---|---|---|---|
| Ignite Spring Properties Xml File | ignite-spring-properties-xml-file | Ignite spring configuration file, <path>/<ignite-configuration>.xml. If the configuration file is not provided, default Ignite configuration configuration is used which binds to 127.0.0.1:47500..47509 | ||
| Ignite Cache Name | ignite-cache-name | The name of the ignite cache | ||
| Ignite Cache Entry Identifier | ignite-cache-entry-identifier | A FlowFile attribute, or attribute expression used for determining Ignite cache key for the Flow File content Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
| Name | Description |
|---|---|
| success | All FlowFiles that are written to Ignite cache are routed to this relationship |
| failure | All FlowFiles that cannot be written to Ignite cache are routed to this relationship |
| Name | Description |
|---|---|
| ignite.cache.get.failed.reason | The reason for getting entry from cache |