Repository navigation
docs: Document the convention for internal public APIs #25495
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
2010YOUY01
merged 4 commits into
apache:main
from
2010YOUY01:codex/internal-public-api-convention
Sep 22, 2026
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -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. | ||
| 2. Operator APIs required by the optimizer to inspect or rewrite execution plans | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nit: Please add another example - benchmarks, which was the original reason why |
||
| 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 | ||
|
|
||
Oops, something went wrong.
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.
There was a problem hiding this comment.
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_helpersfor example) to mark that they are not part of the public API rather than marking them as a doc