alamb opened a new pull request, #26751:
URL: https://github.com/apache/datafusion/pull/26751

   ## Which issue does this PR close?
   
   - N/A (documentation only)
   
   ## Rationale for this change
   
   Nuno Faria's new blog post, [Best Practices for Single Row Lookups (Point 
Queries)](https://datafusion.apache.org/blog/2026/10/24/point-queries/) 
(source: https://github.com/apache/datafusion-site/pull/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?
   
   - Add the blog post to the Good Reads list in `concepts-readings-events.md`
   - Add a "Point Queries (Single Row Lookups)" section to the Tuning Guide in 
`configs.md` summarizing 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 details
   - The Tuning Guide text lives in `dev/update_config_docs.sh`, so that script 
is updated and `configs.md` regenerated from it
   
   ## What is the testing strategy for this PR?
   
   Documentation only. Ran `./dev/update_config_docs.sh` and 
`./ci/scripts/doc_prettier_check.sh --write --allow-dirty`; the generated 
`configs.md` matches.
   
   ## Are there any user-facing changes?
   
   Documentation only.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to