fix(db): write to cutoff table if writeEslTableOnly=true #1893
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If we were previously running with
db.writeEslTableOnly=true
, but now are running withdb.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