Repository navigation
Conversation
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
github-actions
Bot
added
documentation
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
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?
Rationale for this change
Nuno Faria's new blog post, Best Practices for Single Row Lookups (Point Queries) (source: apache/datafusion-site#209), collects practical guidance for getting sub-millisecond point queries out of DataFusion and Parquet.
It should be listed with the other blog posts on the Good Reads page, and the Tuning Guide in the configuration docs currently has nothing about point queries / single row lookups, which is a common use case people ask about.
What changes are included in this PR?
concepts-readings-events.mdconfigs.mdsummarizing the key recommendations from the post (sort by lookup key, small row groups/pages,target_partitions = 1,pushdown_filters, metadata cache, prepared statements) and linking to the post for detailsdev/update_config_docs.sh, so that script is updated andconfigs.mdregenerated from itWhat is the testing strategy for this PR?
Documentation only. Ran
./dev/update_config_docs.shand./ci/scripts/doc_prettier_check.sh --write --allow-dirty; the generatedconfigs.mdmatches.Are there any user-facing changes?
Documentation only.