Livio Spring ee92560f32 fix(projections): handle reduce error by updating failed events (#10726) ...

# Which Problems Are Solved

I noticed that a failure in the projections handlers `reduce` function
(e.g. creating the statement or checking preconditions for the
statement) would not update the `failed_events2` table.
This was due to a wrong error handling, where as long as the
`maxFailureCount` was not reached, the error was returned after updating
the `failed_events2` table, which causes the transaction to be rolled
back and thus losing the update.

# How the Problems Are Solved

Wrap the error into an `executionError`, so the transaction is not
rolled back.

# Additional Changes

none

# Additional Context

- noticed internally
- requires backport to v3.x and v4.x

2025-09-15 18:32:28 +02:00

..

crdb

refactor(fmt): run gci on complete project (#7557)

2024-04-03 10:43:43 +00:00

v2

fix(projections): handle reduce error by updating failed events (#10726)

2025-09-15 18:32:28 +02:00

init.go

fix(projections): pass context to statement execution method (#10328)

2025-07-29 08:58:42 +00:00

statement.go

feat(eventstore): increase parallel write capabilities (#5940)

2023-10-19 12:19:10 +02:00