Performs operations against a cache resource for each message, allowing you to store or retrieve data within message payloads.
This processor will interpolate functions within the
fields individually for each message. This allows you to specify dynamic keys
and values based on the contents of the message payloads and metadata. You can
find a list of functions here.
Deduplication can be done using the add operator with a key extracted from the
message payload, since it fails when a key already exists we can remove the
duplicates using a
cache resource to target with this processor.
The operation to perform with the cache.
A key to use with the cache. This field supports interpolation functions.
A value to use with the cache (when applicable). This field supports interpolation functions.
The TTL of each individual item as a duration string. After this period an item will be eligible for removal during the next compaction. Not all caches support per-key TTLs, and those that do not will fall back to their generally configured TTL setting. This field supports interpolation functions.
Requires version 3.33.0 or newer
An optional array of message indexes of a batch that the processor should apply to. If left empty all messages are processed. This field is only applicable when batching messages at the input level.
Indexes can be negative, and if so the part will be selected from the end counting backwards starting from -1.
Set a key in the cache to a value. If the key already exists the contents are overridden.
Set a key in the cache to a value. If the key already exists the action fails with a 'key already exists' error, which can be detected with processor error handling.
Retrieve the contents of a cached key and replace the original message payload with the result. If the key does not exist the action fails with an error, which can be detected with processor error handling.
Delete a key and its contents from the cache. If the key does not exist the action is a no-op and will not fail with an error.