api: Query isHealthy field as a string to handle JSOnull #2143
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 does this pull request do? Explain your changes. (required)
This fixes the
isHealthy
filter on streams list so we don't get this error:cannot cast jsonb null to type boolean
This happened not when the field was not set, in which case
data->'isHealthy'
returnsa SQL
NULL
but when the field was actually set to a JSONnull
value, which issometimes done here.
Postgres supports converting
NULL
to boolean, but notjsonb null
to boolean, whichis when the query exploded. This fixes it by querying the field as
TEXT
(->>
) instead,which automatically converts
jsonb null
to a SQLNULL
as well and everything works.Also added a little validation that was missing in
parseFilters
.Specific updates (required)
isHealthy
field query to->>
instead of->
parseFilters
How did you test each of these updates (required)
Ran queries on Postgres DB.
Does this pull request close any open issues?
https://discord.com/channels/423160867534929930/611650333243867170/1231996105433157632
Checklist