Coerce boolean type for filter expression#18551
Merged
martint merged 1 commit intotrinodb:masterfrom Aug 9, 2023
Merged
Conversation
5579026 to
7f6bc97
Compare
Member
|
This does not need a release note entry @martint ? |
Member
|
No, it just changes how an error surfaces to the user |
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
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
The following query fails with INTERNAL_ERROR:
Full stacktrace:
I made a related fix to reject non-boolean filter expression in #18460 recently but it seems better to coerce boolean type for filter expression there to cover this case.
Additional context and related issues
Release notes
(x) This is not user-visible or is docs only, and no release notes are required.