stevomitric opened a new pull request, #56812: URL: https://github.com/apache/spark/pull/56812
### What changes were proposed in this pull request? Tests-only coverage for equi-JOINs over the nanosecond-precision timestamp types `TIMESTAMP_NTZ(p)` / `TIMESTAMP_LTZ(p)` (`p` in `[7, 9]`). One new suite, `TimestampNanosJoinSuiteBase`, with `AnsiOn` / `AnsiOff` subclasses. The headline assertion is sub-microsecond **join-key** correctness: every key in the test relations shares the same `epochMicros` and differs only in `nanosWithinMicro`, so a correct join must be driven by the full nanos value — - a fully-equal key (incl. the sub-microsecond remainder) must join, - an `epochMicros`-equal-but-`nanosWithinMicro`-distinct key must **not** join, - NULL keys must not match. ### Why are the changes needed? Joins over the nanosecond types already work (they ride on the hashing / ordering / `UnsafeRow` primitives), but there was no join coverage — Spark's join suites are organized by join type/strategy, not by column type. This locks the behaviour in, mirroring the MIN/MAX follow-up which was likewise tests-only. ### Does this PR introduce _any_ user-facing change? No, tests only. ### How was this patch tested? New suites in this PR. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Opus 4.8) -- 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]
