viirya opened a new pull request, #59455: URL: https://github.com/apache/spark/pull/59455
### What changes were proposed in this pull request? This reverts two backports from branch-3.5: - 37841677112 [SPARK-60071][3.5][SQL] Use identity equality for HybridRowQueue (#59415) - 2378a96f836 [SPARK-60211][4.1][PYTHON] Fix applyInPandasWithState failure with PyArrow 26 due to float slice offsets (cherry-picked from #59423) Both reverts apply cleanly, and the resulting tree is identical to branch-3.5 at aca614f7215, before these two commits. ### Why are the changes needed? Both are bug fixes, not security fixes. Per the [versioning policy](https://spark.apache.org/versioning-policy.html), branch-3.5 is in an extended LTS period during which it only takes security fixes. I backported these two before I was aware of that; @dongjoon-hyun pointed it out on #59450. Neither fix is needed on this branch to keep it working: SPARK-60211 only matters for PyArrow 26, while branch-3.5 requires `pyarrow<13.0.0` (`dev/requirements.txt`) and its CI uses PyArrow 12.0.1. Both fixes stay in branch-4.0 and later. ### Does this PR introduce _any_ user-facing change? It restores the branch-3.5 behavior before the two backports, which has not been in any 3.5 release: `HybridRowQueue` uses case-class equality again, and `applyInPandasWithState` does not convert the slice offsets to `int`. ### How was this patch tested? The resulting tree is identical to aca614f7215, whose branch-3.5 CI run passed. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Opus 5.5) This pull request and its description were written by Isaac. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
