v1.21.0
What's Changed
This release slightly changes the behavior of consumers under the new consumer API for fetch()
and next()
. These operations are now succeptible to consumer deleted type errors. Since these operations are expected to finish at some point (when the number of requested messages is retrieved or when the operation expires) it seems appropriate to telegraph these errors. If your service expects to recover, it can re-issue the next()
or fetch request again. For consume()
, a new option was added abort_on_missing_resource
which instructs the client to cancel if it detects that the stream or the consumer are gone. By default the client will attempt to consumer again.. These options are rejected for order consumer. For more information see #667
Also notable is the addition of a bind
option for consume()
, fetch()
, and next()
. This option will NOT check the status of the consumer or if there's an error during a request for messages. Note that in most cases if the consumer is deleted these will surface as heartbeats missed on the consumer status. For fetch()
and next()
these will result on no messages. Note that when this option is issued the client cannot provide a more precise status. Note that this option is not applicable to ordered consumers. For more information see #668
- [FEAT] [JS] [KV] allow internal kv watch consumer to use filtered consumer api by @aricart in #662
- [CHANGE] [JS] [CONSUMERS]
fetch()
/next()
can fail on consumer/stream errors by @aricart in #667 - [FEAT] [JS] [CONSUMERS] added a
bind
option to theconsume()
,fetch()
,next()
- note this option is not supported in ordered consumers. by @aricart in #668 - [FEAT] [JS] jetstream options also support jsm options by @ramonberrutti in #666 and #669
- [FIX] [JS] jetstreamManager(
checkAPI
) overrode thecheckAPI
option incorrectly by @aricart in #672 - [TEST] fix timer leak detected by tests on consumer reset by @aricart in #664
- [FEAT] [CORE] enhancements to downstream iterator use to determine if the iterator failed by @aricart in #665
New Contributors
- @ramonberrutti made their first contribution in #666
Full Changelog: v1.20.1...v1.21.0