Update Cassandra to write history tasks to new columns #6685
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.
What changed?
Why?
This is a followup change of #6671. We want to migrate Cassandra's transfer, timer, replication task data from typed columns to encoded blob columns introduced in that PR. After this change Cassandra will be in "dual write" mode.
Another followup PR will be created to allow specifying which column we read data from. Currently, we still read history tasks from the original columns as before.
No backfill is required for transfer tasks and replication tasks because old data not inserted with "dual write" mode will be gone soon after the deployment of this PR. A backfill process is required for timer tasks.
How did you test it?
Unit test, manual tests in dev2 environment, persistence test will be created in the followup PR that enables migration on reading tasks
Potential risks
tasks not encoded correctly (no impact production until we enable migration on reading tasks), history task processing might be broken
Release notes
Documentation Changes