Implement IN and NOT_IN filters in FilterOperand class (#12285 fix) #12305
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.
Fix #12285, #12305
Added IN and NOT_IN cases to the FilterOperand class and TransformOperandFactory classes. The PR is related to the 12285 bug: using of the IN expression in the CASE statement within the projection part of the SELECT multistage query. When this expression is used, the query execution fails with an IllegalStateException error, indicating that the function IN cannot be found.