-
Notifications
You must be signed in to change notification settings - Fork 881
fix: use next_event_id column as source of truth when reading workflow execution from Cassandra #7738
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
Merged
fimanishi
merged 6 commits into
cadence-workflow:master
from
fimanishi:use-denormalized-columns-as-source-of-truth-when-reading-execution-record
Feb 26, 2026
Merged
fix: use next_event_id column as source of truth when reading workflow execution from Cassandra #7738
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
f32fa9f
fix: read from denormalized execution columns
fimanishi b0322b8
keep reading from the blob and overwrite when the denormalized column…
fimanishi f0847c7
do not read workflow_state because it is only used in current workflo…
fimanishi 3a4aed9
remove workflow_state from full execution blob test
fimanishi 28c5a38
use comma-ok to prevent panic when getting execution from result
fimanishi 9bb9673
remove next_event_id fallback. CurrentExecution do not use next_event…
fimanishi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a duplicate way to do what the key/value map iteration above is doing - why do we need this too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is from the result not the execution. The data is duplicated in the db, but we use the
next_event_idcolumn for conditional writes. The key/value map iteration is only exploring the execution field data, not the whole execution recordThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
currently, this serves as a fallback, we should remove the logic setting this value when iterating the map
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that makes sense. The only thing here is that we use the same path for current executions (although we don't populate the execution blob in there). Are you ok with removing it or is it ok to leave the fallback?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should remove it