[SQL] Fix bug in compilation of queries with interned strings #5392
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.
Prior to this fix the compiler would crash with an assertion error:
The reason for this is that both nullable and non-nullable strings are represented by nullable InternedString objects, so the nullability of the data changes. The fix is to avoid wrapping in Some any InternedString - they are already option values.
I have also changed a call to a Calcite API which has been modified and will no longer compile on newer versions of Calcite.