I
- IGNORE_DELETE - enum entry in eu.vstoyanov.natsy.jetstream.model.KvWatchOption
Drop DELETE and PURGE markers, leaving only live values
The filter is applied by the client, not the server (
io/nats/client/impl/NatsKeyValueWatchSubscription.java:75-77), so a key whose latest revision is a deletion is simply absent: a cache warmed this way cannot tell "never existed" from "deleted".- IGNORE_DELETE - enum entry in eu.vstoyanov.natsy.jetstream.model.ObjectWatchOption
Drop the markers left by deleted objects, leaving only live ones
The filter is applied by the client, not the server (
io/nats/client/impl/NatsObjectStoreWatchSubscription.java:64), so an object whose latest revision is a deletion is simply absent: a cache warmed this way cannot tell "never existed" from "deleted". ObjectStoreInfo.deleted is how the un-optioned watch reports the same thing without losing the entry.- INCLUDE_HISTORY - enum entry in eu.vstoyanov.natsy.jetstream.model.KvWatchOption
Start at the first revision of every matching key rather than the latest
DeliverPolicy.All(io/nats/client/impl/NatsKeyValueWatchSubscription.java:49): the whole retained history replays before the initial snapshot is complete.- INCLUDE_HISTORY - enum entry in eu.vstoyanov.natsy.jetstream.model.ObjectWatchOption
Start at the first retained metadata revision of every object rather than the latest
DeliverPolicy.All(io/nats/client/impl/NatsObjectStoreWatchSubscription.java:44), which replays every metadata message the bucket still holds rather than the last one per object.In a bucket written through jnats this changes nothing, and the option is here because jnats offers it rather than because it can do what its Key-Value namesake does. Every metadata write carries
Nats-Rollup: sub(io/nats/client/support/NatsObjectStoreUtil.java:63-66,io/nats/client/support/NatsJetStreamConstants.java:114-115) against a stream built withallowRollup(true)(io/nats/client/api/ObjectStoreConfiguration.java:215), so the server purges an object's earlier metadata as each new revision lands: at most one survives per object, andAllandLastPerSubjectsee the same set. An object store keeps no history to replay, so where KvWatchOption.INCLUDE_HISTORY widens the snapshot this only reorders it - by stream sequence rather than by subject.- info(java.lang.String) - function in eu.vstoyanov.natsy.jetstream.ObjectStore
- Get information about an object
- initCause(java.lang.Throwable) - function in kotlin.Throwable
- inProgress() - function in eu.vstoyanov.natsy.jetstream.JetStreamMessage
- Signal that processing is still in progressExtends the acknowledgment deadline for long-running message processing.
- INSTANT - enum entry in eu.vstoyanov.natsy.jetstream.ReplayPolicy
Replay messages as fast as possible
- INTEREST - enum entry in eu.vstoyanov.natsy.jetstream.RetentionPolicy
Retain messages based on interest (consumers)
- isBucketLink() - function in eu.vstoyanov.natsy.jetstream.model.ObjectStoreLink
- Whether this points at a whole bucket, which no read of this store can follow.
- isDelete() - function in eu.vstoyanov.natsy.jetstream.model.KeyValueEntry
- Check if this is a DELETE operation
- isEmpty() - function in eu.vstoyanov.natsy.jetstream.JetStreamBatch
- Check if the batch is empty
- isLatest() - function in eu.vstoyanov.natsy.jetstream.model.KeyValueEntry
- Check if this entry is the latest for the key
- isNotEmpty() - function in eu.vstoyanov.natsy.jetstream.JetStreamBatch
- Check if the batch has messages
- isPurge() - function in eu.vstoyanov.natsy.jetstream.model.KeyValueEntry
- Check if this is a PURGE operation
- isPut() - function in eu.vstoyanov.natsy.jetstream.model.KeyValueEntry
- Check if this is a PUT operation
- isRedelivered() - function in eu.vstoyanov.natsy.jetstream.JetStreamMessage
- Check if this message is a redelivery