Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -293,9 +293,11 @@ impl HashTableLookupExpr {
/// * `random_state` - SeededRandomState for hashing
/// * `map` - Map to check membership (hash table or array map)
/// * `description` - Description for debugging
/// # Note
/// This is public for internal testing purposes only and is not
/// guaranteed to be stable across versions.
///
/// # Public Only for Internal Use:
/// `datafusion-proto` tests require this constructor, but it is not part of
/// the supported public API.
#[doc(hidden)]
pub fn new(
on_columns: Vec<PhysicalExprRef>,
random_state: SeededRandomState,
Expand Down
29 changes: 29 additions & 0 deletions docs/source/contributor-guide/api-health.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,35 @@ Examples of non-breaking changes include:
- Marking a function as deprecated (`#[deprecated]`)
- Adding a new function to a `trait` with a default implementation

### DataFusion-internal Public APIs

Some internal implementation details require `pub` visibility because they are
shared across DataFusion crates. These APIs are not intended as downstream
extension points. They are hidden from generated documentation and are not part
of DataFusion's supported public API, so they may be changed or removed without
notice or a deprecation period. Examples include:

1. Test helpers.

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.

I think in general multiple types of APIs just makes DataFUsion more complicated and I would like to suggest we minimize the number of such APIs as much as possible

For example, for test helpers, we could potentially use a feature (test_helpers for example) to mark that they are not part of the public API rather than marking them as a doc

2. Operator APIs required by the optimizer to inspect or rewrite execution plans

@rluvaton rluvaton Sep 22, 2026 •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Nit: Please add another example - benchmarks, which was the original reason why GroupColumn was exposed and now people use it which complicate changing its api

across crate boundaries.

For APIs intended only for internal use, add `#[doc(hidden)]` and a doc comment
section headed `# Public Only for Internal Use:`. Name the crate or component
that requires access and explain why the API is not intended for downstream use.
For example:

```txt
impl HashTableLookupExpr {
/// ...
///
/// # Public Only for Internal Use:
/// `datafusion-proto` tests require this constructor, but it is not part of
/// the supported public API.
#[doc(hidden)]
pub fn new(...) {...}
}
```

### What is the public SQL API and what is a breaking SQL change?

DataFusion is also used as a SQL engine, so changes to SQL semantics (the
Expand Down
Loading