Repository navigation
fix: preserve TRY overflow semantics in nested integer arithmetic - #7379
Merged
Merged
Conversation
sunchao
added
the
run-spark-4.1-tests
github-actions
Bot
added
bug
viirya
approved these changes
Nov 1, 2026
viirya
left a comment
viirya
left a comment
Member
There was a problem hiding this comment.
LGTM. Comparing against expr.evalMode rather than only TRY also covers an ANSI Add that ends up under a LEGACY one after CollapseProject, e.g. from a view created with ANSI enabled.
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
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 #7378.
Rationale for this change
With ANSI mode disabled, Spark returns
NULLfortry_add(a, b) + bwhen the inner addition overflows. Comet flattened both additions and rebuilt them using the outer operation's wrapping overflow behavior. The same problem affectedtry_multiplyinside a multiplication.What changes are included in this PR?
Only flatten a nested
AddorMultiplywhen its evaluation mode matches the parent. This keeps the inner overflow check in the native expression and still balances chains of legacy integer operations.How are these changes tested?
Added one query to the existing arithmetic SQL fixture covering both operators. With
a = 2147483647andb = 1, the query produced the following results on Spark 4.1.3.try_add(a, b) + btry_multiply(a, a) * bNULLNULLNULLNULLThe full
expressions/math/arithmetic.sqlfixture passed on Spark 3.5.9 and 4.1.3. The existing deep integral Add/Multiply chain test also passed on Spark 4.1.3. These runs compiled the changed serializer against cached Apache Comet dependencies and used the existing native library. Spotless passed.