zhengruifeng opened a new pull request, #57421: URL: https://github.com/apache/spark/pull/57421
### What changes were proposed in this pull request? This follow-up to https://github.com/apache/spark/commit/bc72d936a702cca196a597047b3ca0bf190235d4 aligns the nanosecond timestamp protocol fields with Spark signed integer types. - Changes the nanos remainder and precision fields for both NTZ and LTZ timestamp literals from `uint32` to `int32`. - Changes the timestamp-nanos data type precision fields to `int32` and documents that an omitted precision defaults to 9. - Regenerates the affected Python protobuf descriptors. ### Why are the changes needed? These values are represented as signed `Int` values in Spark. The valid ranges remain non-negative (precision 7 through 9; nanos within a microsecond 0 through 999), so the schema keeps the same field numbers and behavior while matching the rest of Spark. This PR remains protocol-only; no Connect server converters consume these messages yet. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? - Ran `./dev/connect-gen-protos.sh` successfully to regenerate the Python protobuf descriptors. - Ran `git diff --check` successfully. - Attempted `buf lint`, but the locally installed Buf reports existing repository-wide lint violations in unrelated proto files. - Attempted a focused Python descriptor assertion, but the available protobuf runtime predates the regenerated code. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Codex (GPT-5) -- 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]
