While the goal is for TimestampNTZ in the native code to be compatible with Spark, it might be a good idea to hold off on this specific improvement until we review and overhaul the timestamp handling in general (and TimestampNTZ in particular).
On Sat, Jan 24, 2026 at 8:16 AM Vignesh Siva <[email protected]> wrote: > Hi all, > > I’m working on issue #3180 related to incorrect timezone conversion for > hour/minute/second on TimestampNTZ inputs. > > While preparing a fix, I wanted to clarify the intended direction: > > Is the goal to fully support Spark-compatible TimestampNTZ semantics > directly in the Rust implementation (i.e., bypassing timezone conversion), > or is TimestampNTZ expected to remain unsupported at the Scala serde layer > until the broader Comet timezone handling work is completed? > > I’d like to ensure the fix aligns with the long-term design rather than > introducing behavior that may be reconsidered later. > > Thanks for the guidance, > Vignesh >
