cache
Stores each message in a cache.
Caches are configured as resources, where there’s a wide variety to choose from.
:cache-support: aws_dynamodb=certified, aws_s3=certified, file=certified, memcached=certified, memory=certified, nats_kv=certified, redis=certified, ristretto=certified, couchbase=community, mongodb=community, sql=community, multilevel=community, ttlru=community, gcp_cloud_storage=community, lru=community, noop=community
The target
field must reference a configured cache resource label like follows:
In order to create a unique key
value per item you should use function interpolations described in Bloblang queries.
Performance
This output benefits from sending multiple messages in flight in parallel for improved performance. You can tune the max number of in flight messages (or message batches) with the field max_in_flight
.
Fields
target
The target cache to store messages in.
Type: string
key
The key to store messages by, function interpolation should be used in order to derive a unique key for each message. This field supports interpolation functions.
Type: string
Default: "${!count(\"items\")}-${!timestamp_unix_nano()}"
ttl
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.
Type: string
Requires version 3.33.0 or newer
max_in_flight
The maximum number of messages to have in flight at a given time. Increase this to improve throughput.
Type: int
Default: 64