Skip to content

docs: Rewrite supported expressions page to show complete overview of what is and is not supported by Comet#4550

Merged
andygrove merged 27 commits into
apache:mainfrom
andygrove:docs-expression-support-reference
Jun 2, 2026
Merged

docs: Rewrite supported expressions page to show complete overview of what is and is not supported by Comet#4550
andygrove merged 27 commits into
apache:mainfrom
andygrove:docs-expression-support-reference

Conversation

@andygrove
Copy link
Copy Markdown
Member

@andygrove andygrove commented Jun 1, 2026

Which issue does this PR close?

Closes #.

Rationale for this change

  • Use SQL function name rather than Spark class name - more appropriate for end users and easier to reconcile to Spark code
  • Show all Spark expressions and current Comet status (supported, supported with incompatibilities, out of scope, etc)

What changes are included in this PR?

See rendered version.

How are these changes tested?

andygrove added 26 commits June 1, 2026 12:07
…scope section, reclassify aes_* as codegen-dispatch candidates
…-of-scope; mark literal-resolving funcs supported
…ve list; drop fully out-of-scope csv/xml sections
@andygrove andygrove changed the title docs: Rewrite supported expressions page to show complete overview of what is and is not supported by Comet [WIP] docs: Rewrite supported expressions page to show complete overview of what is and is not supported by Comet Jun 1, 2026
@andygrove andygrove marked this pull request as ready for review June 1, 2026 21:11
narrow real-world analytics use and high implementation cost. These will fall back to Spark and
are not on the roadmap:

- **Probabilistic sketches and approximate top-k** (`kll_sketch_*`, `hll_*`, `theta_*`, `count_min_sketch`, `bitmap_*`, `approx_top_k*`): specialized data structures with exact-correctness traps.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

those are very popular in distinct aggregation which allows some approximation, would it be correct to outscope, or move to later phases in roadmap?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you think we can implement these natively with 100% compatibility? I haven't looked into this


---

## Out-of-scope function list
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

isn't it duplicate?

- **User-defined functions:** Scala UDFs registered through the DataFrame or SQL API.
- **Structural expressions:** aliases, attribute references, literals, sort orders, and `CASE WHEN`.

This list is illustrative, not exhaustive: the per-function tables are not the complete set of expressions Comet can accelerate.
Copy link
Copy Markdown
Contributor

@comphead comphead Jun 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

from the text in this section it is not clear if such cases supported/planned or falls back

…ount_distinct and uuid; move approx_percentile to not-planned; remove redundant end list
Copy link
Copy Markdown
Contributor

@comphead comphead left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @andygrove

@andygrove andygrove marked this pull request as draft June 1, 2026 22:42
@andygrove andygrove marked this pull request as ready for review June 1, 2026 22:46
@andygrove andygrove merged commit d55fc9c into apache:main Jun 2, 2026
15 checks passed
@andygrove andygrove deleted the docs-expression-support-reference branch June 2, 2026 13:13
@andygrove
Copy link
Copy Markdown
Member Author

Merged. Thanks @comphead. Let's keep iterating on this. Docs PRs are cheap now. Everyone should feel free to create PRs to make edits for these pages. I'm going to be updating this as other pending PRs are merged to mark more expressions as implemented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants