Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(db): write to cutoff table if writeEslTableOnly=true #1893

Merged
merged 3 commits into from
Aug 30, 2024

Conversation

sven-urbanski-freiheit-com
Copy link
Contributor

@sven-urbanski-freiheit-com sven-urbanski-freiheit-com commented Aug 16, 2024

If we were previously running with db.writeEslTableOnly=true, but now are running with db.writeEslTableOnly=false (which is the recommended way to enable the database), then we would have many events in the event_sourcing_light table that have not been processed - possibly over days or weeks. We must not apply events that are that outdated!

So, we write the current transformer to the cutoff, so it doesn't get processed, when we are using only the esl table

Ref: SRX-KNBOC7

If we were previously running with `db.writeEslTableOnly=true`, but now are running with
`db.writeEslTableOnly=false` (which is the recommended way to enable the database),
then we would have many events in the event_sourcing_light table that have not been processed -
possibly over days or weeks. We must not apply events that are that outdated!

So, if there is no cutoff yet, we write the current transformer to the cutoff,
so it doesn't get processed.

Ref: SRX-KNBOC7
@miguel-crespo-fdc miguel-crespo-fdc merged commit dcadfbd into main Aug 30, 2024
18 checks passed
@miguel-crespo-fdc miguel-crespo-fdc deleted the su-fix-cutoff branch August 30, 2024 10:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants