[GitHub] [ignite] alex-plekhanov commented on a diff in pull request #10002: IGNITE-15189 Documentation: Calcite-based SQL engine

[GitBox <gi...@apache.org>]

alex-plekhanov commented on code in PR #10002:
URL: https://github.com/apache/ignite/pull/10002#discussion_r861483202


##########
docs/_docs/SQL/sql-introduction.adoc:
##########
@@ -22,7 +22,7 @@ You can interact with Ignite as you would with any other SQL enabled storage by
 
 Internally, SQL tables have the same data structure as link:data-modeling/data-modeling#key-value-cache-vs-sql-table[key-value caches]. It means that you can change partition distribution of your data and leverage link:data-modeling/affinity-collocation[affinity colocation techniques] for better performance.
 
-Ignite's SQL engine uses H2 Database to parse and optimize queries and generate execution plans.
+Ignite's default SQL engine uses H2 Database to parse and optimize queries and generate execution plans, but also the Apache Calcite-based SQL engine can be enabled to execute queries (experimental feature, see link:SQL/sql-calcite[Calcite-based SQL engine]).

Review Comment:
   "Optimize queries and generate execution plans" are phases of "execute queries", these phases can be run using H2 or using Calcite, so Calcite-based engine - it's just an alternative, but not a add-on to do some additional work. I think your suggestion is not quite correct. 



-- 
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: notifications-unsubscribe@ignite.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org