refine docs

alibaba · Jan 17, 2025 · 95f34ab · 95f34ab
1 parent 971025a
commit 95f34ab
Showing 1 changed file with 4 additions and 3 deletions.
diff --git a/docs/interactive_engine/gopt.md b/docs/interactive_engine/gopt.md
@@ -349,9 +349,10 @@ Design of GOpt
 :::
 
 ### Detailed Introduction
-A comprehensive introduction to GOpt will be provided in subsequent sections. Please stay tuned for detailed updates and information.
 
-#### Rules 
+#### Rules
+
+Rules play a pivotal role in GOpt’s optimization framework, enabling efficient and effective query transformations. Below is an outline of some key rules implemented in GOpt:
 
 **ScanEarlyStopRule**: Pushes the limit operation down to the scan node. During the scan process, the scan stops as soon as the specified limit count is reached.
    
@@ -365,4 +366,4 @@ Although the query involves Scan and GetV steps, their results are not directly
 Match (a:PERSON)-[b:LIKES]->(c:COMMENT) Return b.name;
 ```
 
-**TopKPushDownRule**: This rule pushes down topK operations to the project node and is based on Calcite's [SortProjectTransposeRule](https://calcite.apache.org/javadocAggregate/org/apache/calcite/rel/rules/SortProjectTransposeRule.html), leveraging the original rule wherever possible. However, in our more complex distributed scenario, deferring the execution of the project node can disrupt already sorted data. To address this, we modified the matching logic in `SortProjectTransposeRule`. Currently, the PushDown operation is applied only when the sort fields are empty, which means only the limit is pushed down to the project node.
+**TopKPushDownRule**: This rule pushes down topK operations to the project node and is based on Calcite's [SortProjectTransposeRule](https://calcite.apache.org/javadocAggregate/org/apache/calcite/rel/rules/SortProjectTransposeRule.html), leveraging the original rule wherever possible. However, in our more complex distributed scenario, deferring the execution of the project node can disrupt already sorted data. To address this, we modified the matching logic in `SortProjectTransposeRule`. Currently, the PushDown operation is applied only when the sort fields are empty, which means only the limit is pushed down to the project node.