This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/datafusion.git
The following commit(s) were added to refs/heads/main by this push:
new de40f0c9f5 Docs: Fix some links in docs (#19834)
de40f0c9f5 is described below
commit de40f0c9f54a11854f784bc3fe65bababec96ff4
Author: Andrew Lamb <[email protected]>
AuthorDate: Thu Jan 15 17:50:28 2026 -0500
Docs: Fix some links in docs (#19834)
Small doc tweaks
---
docs/source/library-user-guide/query-optimizer.md | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/docs/source/library-user-guide/query-optimizer.md
b/docs/source/library-user-guide/query-optimizer.md
index 8ed6593d56..b70ff38575 100644
--- a/docs/source/library-user-guide/query-optimizer.md
+++ b/docs/source/library-user-guide/query-optimizer.md
@@ -25,11 +25,12 @@ format.
DataFusion has modular design, allowing individual crates to be re-used in
other projects.
This crate is a submodule of DataFusion that provides a query optimizer for
logical plans, and
-contains an extensive set of [`OptimizerRule`]s and [`PhysicalOptimizerRules`]
that may rewrite the plan and/or its expressions so
+contains an extensive set of [`OptimizerRule`]s and [`PhysicalOptimizerRule`]s
that may rewrite the plan and/or its expressions so
they execute more quickly while still computing the same result.
[`optimizerrule`]:
https://docs.rs/datafusion/latest/datafusion/optimizer/trait.OptimizerRule.html
-[`physicaloptimizerrules`]:
https://docs.rs/datafusion/latest/datafusion/physical_optimizer/trait.PhysicalOptimizerRule.html
+[`physicaloptimizerrule`]:
https://docs.rs/datafusion/latest/datafusion/physical_optimizer/trait.PhysicalOptimizerRule.html
+[`logicalplan`]:
https://docs.rs/datafusion/latest/datafusion/logical_expr/enum.LogicalPlan.html
## Running the Optimizer
@@ -75,7 +76,7 @@ Please refer to the
example to learn more about the general approach to writing optimizer rules and
then move onto studying the existing rules.
-`OptimizerRule` transforms one ['LogicalPlan'] into another which
+`OptimizerRule` transforms one [`LogicalPlan`] into another which
computes the same results, but in a potentially more efficient
way. If there are no suitable transformations for the input plan,
the optimizer can simply return it as is.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
