Guidance on handling TimestampNTZ semantics in Comet #3277
Unanswered
vigneshsiva11
asked this question in
Q&A
Replies: 1 comment
-
|
@vigneshsiva11 , thank you for bringing this up issue. I believe gating it on scala side could be good first step to not panic the execution. Also I am curious if you have a github issue you could share with some steps to replicate the issue ? Also tagging @parthchandra who worked on this area in Arrow , DF and Comet |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
While working on fixes related to TimestampNTZ behavior in Comet, I noticed that some correctness issues can be handled either in the Rust execution layer or by gating unsupported cases in the Scala serde layer.
With ongoing work to add broader TimestampNTZType support, is there a preferred guideline for contributors on where such fixes should live (Rust vs Scala) while the feature is still evolving?
Beta Was this translation helpful? Give feedback.
All reactions