fix: add scalar support for bit_count expression #3361
+55
−8
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.
The bit_count function now handles scalar inputs in addition to arrays. Scalar inputs return scalar outputs, maintaining proper type semantics.
Enable bit_count tests in bitwise.sql
Which issue does this PR close?
Closes #3341
Rationale for this change
Current implementation doesn't take scalar input.
What changes are included in this PR?
Boolean,Byte,Short,IntegerandLonglike Spark does.How are these changes tested?
CometBitwiseExpressionSuite.scalaby disablingConstantFolding.