docs: adopt issue #4419 terminology in Understanding Comet Plans guide#4650
Open
andygrove wants to merge 1 commit into
Open
docs: adopt issue #4419 terminology in Understanding Comet Plans guide#4650andygrove wants to merge 1 commit into
andygrove wants to merge 1 commit into
Conversation
…s guide Replace bare uses of "native" with precise terms from the terminology framework: "Rust-implemented" / "implemented in Rust" for the implementation language, "Comet pipeline" for pipeline membership, and "runs in Comet" / "falls back to Spark" for fallback. Keep the compound forms the issue allows (native Rust, native shuffle, and operator names such as CometNativeScan).
comphead
reviewed
Jun 13, 2026
| A "fallback" happens when Comet cannot translate part of a plan into native | ||
| execution. Fallback can be partial (a subtree falls back while the rest stays | ||
| native) or full (no Comet nodes appear). | ||
| A "fallback" happens when Comet cannot run part of a plan in the Comet |
Contributor
There was a problem hiding this comment.
should we also mention fallback to columnar?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Part of #4419.
Rationale for this change
Issue #4419 points out that the word "native" is overloaded across Comet's docs, carrying three different meanings (Rust implementation, Comet pipeline membership, and scan type). The issue proposes a terminology framework that keeps a few unambiguous compound forms (such as "native Rust", "native shuffle", and operator names like
CometNativeScan) but otherwise replaces bare "native" with precise terms.The "Understanding Comet Plans" page is the central user-facing doc that explains these concepts, so it is the highest-impact place to start. This PR keeps the change focused on that one page rather than attempting to clean up every doc at once.
What changes are included in this PR?
In
docs/source/user-guide/latest/understanding-comet-plans.md:How are these changes tested?
Documentation-only change. Verified with
prettier --check.