Minor: Add Architectural Goals to the docs #11109
Merged
Conversation
This file contains 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
github-actions
bot
removed
the
documentation
findepi
pushed a commit
to findepi/datafusion
that referenced
this pull request
Jul 16, 2024
* Minor: Add Architectural Goals to the docs * Update datafusion/core/src/lib.rs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #7013
Rationale for this change
As I give various presentations like #10969 I have been describing the emergent design principles of DataFusion. But I could not find them documented anywhere
Let's document the emergent principles -- I don't intend that this changes anything about DataFusion, I am simply trying to describe the current reality
What changes are included in this PR?
CustominzingsectionArchitectureoverviewAre these changes tested?
Are there any user-facing changes?