annagobova commented on code in PR #10983:
URL: https://github.com/apache/ignite/pull/10983#discussion_r1358028749


##########
docs/_docs/SQL/sql-calcite.adoc:
##########
@@ -241,3 +228,150 @@ Below are the data types supported by the Calcite-based 
SQL engine:
 |`java.lang.Object`
 
 |===
+
+== Optimizer hints [[hints]]
+
+The query optimizer does its best to build the fastest excution plan. But it 
is a far way to create an optimizer which
+is the most effective for each case. You may have better knowledge of your 
data design, application design or data
+distribution in the cluster. The SQL hints can help the optimizer to make 
optimizations more rationally or build
+execution plan faster.
+
+[NOTE]
+====
+SQL hints are not mandatory to apply and might be skipped in some cases.
+====
+
+=== Hints format
+Sql hints are defined with the special comment +++/*+ HINT */+++ reffered as 
_hint block_. Spaces before and after the
+hint name are required. Hint block is placed right after a relation operator. 
Usually, after _SELECT_. Several hint

Review Comment:
   — **The** hint block
   
   The hint block is placed right after a relation operator, usually after 
SELECT.



-- 
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]

Reply via email to