viirya opened a new pull request, #57619:
URL: https://github.com/apache/spark/pull/57619

   ### What changes were proposed in this pull request?
   
   Add a test to `ArrowCachedBatchSerializerSuite` that round-trips nanosecond 
timestamps nested inside an array, a struct field, and a map value through the 
Arrow cache, using a value outside the int64 epoch-nanos window (year 3000 at 
nanosecond precision) that the standard interchange encoding cannot represent, 
alongside an in-window value.
   
   ### Why are the changes needed?
   
   The suite covers top-level nanosecond timestamps and nested 
`CalendarInterval`, but had no round trip for nanosecond timestamps nested in 
complex types. The nested path relies on recursion in two places: 
`ArrowWriter`'s field writers dispatch on `(type, vector)` recursively on the 
write side, and on the read side every container accessor in 
`ArrowColumnVector` (struct children, `ArrayAccessor`'s data vector, 
`MapAccessor`'s keys/values) wraps its element vector through the constructor 
that runs the lossless tagged-struct recognizers. A regression at any nesting 
level would silently decode wrong values, so the machinery deserves an 
end-to-end pin for the one lossless type family that has out-of-window domain 
values.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No, test-only.
   
   ### How was this patch tested?
   
   The new test; full `ArrowCachedBatchSerializerSuite` and 
`ArrowCachedBatchKryoRegistrationSuite` pass (76 tests).
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Yes, this pull request and its description were written by Claude Code.


-- 
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]

Reply via email to