ignite-15189 SQL: Optimized code generation for IN statement with lit… #7328
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.
https://issues.apache.org/jira/browse/IGNITE-25289
This pull request introduces enhancements to the handling and expansion of SEARCH/SARG operations for nullable inputs in the SQL engine, modifies SQL engine tests, and adjusts the usage of utility functions across various modules.
Core Updates:
Added new utility methods (expandSearchNullable and expandSearchNullableRecursive) in the RexUtils class to optimize the expansion process for nullable inputs, reducing redundant NULL checks in generated bytecode.
Replaced older RexUtil methods (e.g., expandSearch) with the updated RexUtils alternatives where necessary to improve performance and handle specific nullable cases.
Affected Components:
Justifications:
The main difference with the original patch is the absence of an optimization for JSON plan serialization. Due to this breaking invariance, what we have before serialization should be the same as what we have after deserialization.