fix(#13): record failed events when the listener re-read fails #22

Merged
KofTwentyTwo merged 2 commits from feature/GH-13-listener-reread-failures into develop 2026-10-07 01:50:00 +00:00
2 Commits
Author SHA1 Message Date
james.maes dfac7c3c9a fix(#13): log a failed re-read at once and name a missing class at start
The listener now also catches a LinkageError from the re-read and logs a warn with the table name and record count before deferring the failure rows to the commit, so a rollback still leaves a trace. A LinkageError at start names the missing class and the optional AWS SDK v2 dependencies instead of reporting OpenSearch as unreachable.

Refs #13
2026-10-06 19:06:04 -05:00
james.maes f2703f4818 fix(#13): record failed events when the listener re-read fails
A failed in-transaction re-read of updated records now records their keys in quickSearchFailedEvent after the commit, so basepull replays them. A LinkageError from building or invoking the lazy client and publisher is recorded the same way, and a DEGRADED start tolerates it.

Closes #13
2026-10-06 19:06:04 -05:00