You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ignite.apache.org by GitBox <gi...@apache.org> on 2022/07/28 08:19:47 UTC

[GitHub] [ignite] ptupitsyn commented on a diff in pull request #10001: IGNITE-11404: Document CREATE TABLE "parallelism" option

ptupitsyn commented on code in PR #10001:
URL: https://github.com/apache/ignite/pull/10001#discussion_r931920392


##########
docs/_docs/sql-reference/ddl.adoc:
##########
@@ -51,6 +51,7 @@ sets the write synchronization mode for the underlying cache. If neither this no
 ** `AFFINITY_KEY=<affinity key column name>` - specifies an link:data-modeling/affinity-collocation[affinity key] name which is a column of the `PRIMARY KEY` constraint.
 ** `CACHE_NAME=<custom name of the new cache>` - the name of the underlying cache created by the command.
 ** `DATA_REGION=<existing data region name>` - name of the link:memory-configuration/data-regions[data region] where table entries should be stored. By default, Ignite stores all the data in a default region.
+** `PARALLELISM=<number of SQL execution threads>` - SQL queries are executed in single thread by default on each node involved, but for AP style SQL, the performance of executing in multi thread mode is better, see link:perf-and-troubleshooting/sql-tuning#query-parallelism[Query Parallelism] for details.

Review Comment:
   ```suggestion
   ** `PARALLELISM=<number of SQL execution threads>` - SQL queries are executed by a single thread on each node by default, but certain scenarios can benefit from multi-threaded execution, see link:perf-and-troubleshooting/sql-tuning#query-parallelism[Query Parallelism] for details.
   ```



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