chore: migrate sample event column to text for reporting #5503
+70
−79
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
itsmihir
changed the title
itsmihir
changed the title
itsmihir
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.
Description
Recently, we migrated the jobsDB payload column to the text type; however, in the
reportsanderror_detail_reportstables, we still use the jsonb type to store sample_event. This has led to instances where Postgre failed to cast sample_event from string to jsonb due to special characters, resulting in processor panics.This PR migrates the
sample_eventcolumn in these tables fromjsonbtotextto ensure consistency and prevent such failures.Linear Ticket
< Replace with Linear Link ( create or search linear ticket) or >
Security