You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
What's Changed
News
One can now set a
failure policy
a specific read side.Failure Policies
STOP
: this will completely stop the given readside when the processing of an event failedSKIP
: this will skip the failed processed event and advanced the offset to continue to the next event.REPLAY_SKIP
: this will attempt to replay the failed processed event five times and skip to the next eventREPLAY_STOP
: this will attempt to replay the failed processed event five times and stop the given readsideThere are two ways to achieve this:
Using the yaml file
STOP
,SKIP
,REPLAY_SKIP
,REPLAY_STOP
. If it is not set the default policy is used.Example: read-side-config.yml (multiple read side config in a single yaml file)
Using the environment variables approach
Just set the given read side setting
FAILURE_POLICY
to the failure policy stated aforementioned.Example
For more on how to set a read side setting refer to docs
Full Changelog: v2.3.0...v2.4.0
This discussion was created from the release v2.4.0.
Beta Was this translation helpful? Give feedback.
All reactions