chore(audit): audit bitwise expressions across Spark 3.4.3, 3.5.8, 4.0.1, 4.1.1#4479
Open
andygrove wants to merge 1 commit into
Open
chore(audit): audit bitwise expressions across Spark 3.4.3, 3.5.8, 4.0.1, 4.1.1#4479andygrove wants to merge 1 commit into
andygrove wants to merge 1 commit into
Conversation
…0.1, 4.1.1 Add per-version audit sub-bullets to all 11 supported bitwise SQL function names (`&`, `<<`, `>>`, `^`, `bit_count`, `bit_get`, `getbit`, `shiftright`, `shiftrightunsigned`, `|`, `~`). The Spark expression classes are byte-for-byte identical across the four versions; the only changes are the parser-level operator aliases added in Spark 4.0 (`<<` / `>>` / `>>>` as aliases for `shiftleft`/`shiftright`/`shiftrightunsigned`) and the new `BitShiftOperation` shared base trait. `getbit` is a registry alias of `BitwiseGet` / `bit_get`. No support-level consistency issues were found in the seven backing serdes. `CometShiftLeft` and `CometShiftRight` already correctly cast the `right` operand to `LongType` when needed for DataFusion's matching-operand-type requirement. No new tracking issues are filed.
This was referenced May 28, 2026
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
1 participant
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.
Which issue does this PR close?
Closes #.
Rationale for this change
Continuation of the per-category expression audit. Same pattern as #4478 (map), #4476 (hash), #4475 (conditional), #4474 (misc), #4473 (collection), #4470 (json), #4469 (struct), using the updated
audit-comet-expressionskill in #4468.What changes are included in this PR?
Support-doc audit notes
Add per-version audit sub-bullets to all 11 supported bitwise SQL function names (
&,<<,>>,^,bit_count,bit_get,getbit,shiftright,shiftrightunsigned,|,~). The Spark expression classes are byte-for-byte identical across the four versions for behaviour; the only changes are the parser-level operator aliases added in Spark 4.0 (<</>>/>>>as aliases forshiftleft/shiftright/shiftrightunsigned) and the newBitShiftOperationshared base trait.getbitis a registry alias ofBitwiseGet/bit_get.Support-level consistency fixes
None. The seven backing serdes were already clean.
CometShiftLeftandCometShiftRightalready correctly cast therightoperand toLongTypewhen needed for DataFusion's matching-operand-type requirement.Tracking issues filed for follow-up
None.
Audit process
Audited directly using the
audit-comet-expressionskill (4 Spark versions per #4468). Seven backing serdes, no parallel subagents needed.How are these changes tested?
make coresucceeds (no code changes; doc only).CometBitwiseExpressionSuitecoverage remains unchanged.