Skip to content

docs: apply the style guide's "native" rules to timezones.md - #7477

Open
Abhishek-Mohan wants to merge 1 commit into
apache:mainfrom
Abhishek-Mohan:docs/7358-timezones-native
Open

Abhishek-Mohan wants to merge 1 commit into
apache:mainfrom
Abhishek-Mohan:docs/7358-timezones-native

Conversation

@Abhishek-Mohan

@Abhishek-Mohan Abhishek-Mohan commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

Which issue does this PR close?

Part of #7358. This PR moves contributor-guide/timezones.md over; the other pages stay open in that issue.

Rationale for this change

The style guide from #7151 rules out "runs natively", "the native path" and similar phrases (N1), and, in the contributor guide, allows "native" before a noun only when it names something under native/ or the JNI boundary (N3). timezones.md was one of the pages named in the #7151 review as still using them.

What changes are included in this PR?

One page, docs/source/contributor-guide/timezones.md, eight wording changes:

Before After Rule
feeds another native expression feeds another Rust-implemented expression N3
date_format runs natively only in UTC sessions Comet uses to_char for date_format only in UTC sessions, unless spark.comet.expression.DateFormatClass.allowIncompatible=true N1, P16
has no native spelling has no spelling that Tz::from_str accepts N3
compares the native version (getTzdataVersion) compares the native library's IANA database version (getTzdataVersion) N3
Two Spark settings are not handled natively Comet does not handle two Spark settings N1
the cases the native path cannot handle the cases their Rust implementation cannot handle N1
a native path gated on "the session is UTC" a Rust fast path gated on "the session is UTC" N1
Check that the expression ran natively Check that the expression ran in Rust N1

The date_format row also fixes a claim: CometDateFormat.convert uses to_char outside UTC when the expression's allowIncompatible config is set.

The last row says "in Rust" rather than "in the Comet pipeline" because the sentence contrasts the Rust implementation with codegen dispatch, which also stays in the Comet pipeline.

Uses the guide allows are unchanged: "native code", "native side", "native plan", "native kernel", "native scan", "native implementation", the JVM/native boundary, and expect_native (N2, N3, N6).

How are these changes tested?

Documentation only.

  • Checked each changed claim against the code at the branch head: CometDateFormat and CometConf.getExprAllowIncompatConfigKey (spark/.../serde/datetime.scala, CometConf.scala), CometTimeZone.nativeId, and NativeBase.getTzdataVersion with its Rust side in native/core/src/lib.rs.
  • prettier --check passes on the changed page.
  • Built the docs with Sphinx (-n) at the base and at the head: 32 warnings on each, none new, none on this page.

AI assistance: written with Claude Opus 5.5 through OpenCode.

Replace the phrases the style guide rules out (N1, N3) with the term
each one means: "runs natively", "not handled natively", "the native
path", "a native path" and "ran natively" become what Comet does in
Rust, and "native expression", "native spelling" and "native version"
name the Rust expression, the `Tz::from_str` parser and the native
library's IANA database version.

The `date_format` sentence also said Comet uses `to_char` only in UTC
sessions. `CometDateFormat` also uses it in other sessions when
`spark.comet.expression.DateFormatClass.allowIncompatible=true`, so the
sentence now says so.

Part of apache#7358.

Generated-by: OpenCode
@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Nov 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant