Add support for overriding created_at timestamps for copy transform workflows #282
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Johnabell
force-pushed
the
support-created-at-override
branch
from
002e3e7
to
0bc9bef
Compare
Johnabell
force-pushed
the
support-created-at-override
branch
from
0bc9bef
to
fa9cb36
Compare
Johnabell
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We are looking at running a copy-transform on our event stream.
This involves reading all events out of one event store and filtering/transforming them before writing them to a new event store. To support this we would like to maintain the timestamps on the original events in both the events table and the streams table.
This PR make that possible by allowing the caller to override
created_atwhen appending events to the event store.