[Spark 4.1.0] evalMode access changed to evalContext.evalMode for arithmetic expressions

[res-life]

Summary

In Spark 4.1.0, the evalMode field on arithmetic expressions was moved inside an evalContext object, requiring access via expr.evalContext.evalMode instead of expr.evalMode.

Details

• Spark Version: 4.1.0
• Change Type: API structural change
• Upstream Commit: apache/spark@a96e9ca

Affected Expressions

Expression	Spark ≤4.0.x	Spark 4.1.0+
Add	add.evalMode	add.evalContext.evalMode
Subtract	sub.evalMode	sub.evalContext.evalMode
Multiply	mul.evalMode	mul.evalContext.evalMode
Divide	div.evalMode	div.evalContext.evalMode
Remainder	mod.evalMode	mod.evalContext.evalMode
Sum	sum.evalMode	sum.evalContext.evalMode
Average	avg.evalMode	avg.evalMode (unchanged)

Impact

Code that directly accesses .evalMode on arithmetic expressions will fail to compile against Spark 4.1.0.

Example:

// Before (Spark ≤4.0.x)
val mode = addExpr.evalMode

// After (Spark 4.1.0+)  
val mode = addExpr.evalContext.evalMode

Proposed Solution

Create version-specific TryModeShim objects:

• spark330db/TryModeShim.scala - uses direct .evalMode access
• spark410/TryModeShim.scala - uses .evalContext.evalMode access

Related

• Part of Spark 4.1.0 API compatibility work

[res-life]

I'll finish the shim and make Spark-4.1 building pass, but need to double check potential other impacts.

[res-life]

I'll finish the shim and make Spark 410 shim building pass, but need more investigations about potential impacts, tests.

[res-life]

Will be closed by #14120