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

Reply via email to