[jira] [Updated] (IGNITE-10206) Allow specifying query parallelism in CREATE TABLE's WITH "" clause
[
https://issues.apache.org/jira/browse/IGNITE-10206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-10206:
-
Ignite Flags: Docs Required,Release Notes Required (was: Docs Required)
> Allow specifying query parallelism in CREATE TABLE's WITH "" clause
> ---
>
> Key: IGNITE-10206
> URL: https://issues.apache.org/jira/browse/IGNITE-10206
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.6
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Kuznetsov
>Priority: Minor
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> As in
> {code}
> CREATE TABLE foo (id long primary key, val varchar) WITH "backups=1,
> query_parallelism=4";
> {code}
> upd: actually "parallelism=4"
> Currently it is possible to specify e.g. backups but not query_parallelism.
> This leads to necessity to specify cache template for such tables, which is
> cumbersome.
> Moreover, people may ignore this option outright and get worse performance.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-10206) Allow specifying query parallelism in CREATE TABLE's WITH "" clause
[
https://issues.apache.org/jira/browse/IGNITE-10206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-10206:
-
Fix Version/s: 2.8
> Allow specifying query parallelism in CREATE TABLE's WITH "" clause
> ---
>
> Key: IGNITE-10206
> URL: https://issues.apache.org/jira/browse/IGNITE-10206
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.6
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Kuznetsov
>Priority: Minor
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As in
> {code}
> CREATE TABLE foo (id long primary key, val varchar) WITH "backups=1,
> query_parallelism=4";
> {code}
> upd: actually "parallelism=4"
> Currently it is possible to specify e.g. backups but not query_parallelism.
> This leads to necessity to specify cache template for such tables, which is
> cumbersome.
> Moreover, people may ignore this option outright and get worse performance.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10206) Allow specifying query parallelism in CREATE TABLE's WITH "" clause
[
https://issues.apache.org/jira/browse/IGNITE-10206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kuznetsov updated IGNITE-10206:
-
Description:
As in
{code}
CREATE TABLE foo (id long primary key, val varchar) WITH "backups=1,
query_parallelism=4";
{code}
upd: actully "parallelism=4"
Currently it is possible to specify e.g. backups but not query_parallelism.
This leads to necessity to specify cache template for such tables, which is
cumbersome.
Moreover, people may ignore this option outright and get worse performance.
was:
As in
{code}
CREATE TABLE foo (id long primary key, val varchar) WITH "backups=1,
query_parallelism=4";
{code}
Currently it is possible to specify e.g. backups but not query_parallelism.
This leads to necessity to specify cache template for such tables, which is
cumbersome.
Moreover, people may ignore this option outright and get worse performance.
> Allow specifying query parallelism in CREATE TABLE's WITH "" clause
> ---
>
> Key: IGNITE-10206
> URL: https://issues.apache.org/jira/browse/IGNITE-10206
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.6
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Kuznetsov
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As in
> {code}
> CREATE TABLE foo (id long primary key, val varchar) WITH "backups=1,
> query_parallelism=4";
> {code}
> upd: actully "parallelism=4"
> Currently it is possible to specify e.g. backups but not query_parallelism.
> This leads to necessity to specify cache template for such tables, which is
> cumbersome.
> Moreover, people may ignore this option outright and get worse performance.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10206) Allow specifying query parallelism in CREATE TABLE's WITH "" clause
[
https://issues.apache.org/jira/browse/IGNITE-10206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kuznetsov updated IGNITE-10206:
-
Description:
As in
{code}
CREATE TABLE foo (id long primary key, val varchar) WITH "backups=1,
query_parallelism=4";
{code}
upd: actually "parallelism=4"
Currently it is possible to specify e.g. backups but not query_parallelism.
This leads to necessity to specify cache template for such tables, which is
cumbersome.
Moreover, people may ignore this option outright and get worse performance.
was:
As in
{code}
CREATE TABLE foo (id long primary key, val varchar) WITH "backups=1,
query_parallelism=4";
{code}
upd: actully "parallelism=4"
Currently it is possible to specify e.g. backups but not query_parallelism.
This leads to necessity to specify cache template for such tables, which is
cumbersome.
Moreover, people may ignore this option outright and get worse performance.
> Allow specifying query parallelism in CREATE TABLE's WITH "" clause
> ---
>
> Key: IGNITE-10206
> URL: https://issues.apache.org/jira/browse/IGNITE-10206
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.6
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Kuznetsov
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As in
> {code}
> CREATE TABLE foo (id long primary key, val varchar) WITH "backups=1,
> query_parallelism=4";
> {code}
> upd: actually "parallelism=4"
> Currently it is possible to specify e.g. backups but not query_parallelism.
> This leads to necessity to specify cache template for such tables, which is
> cumbersome.
> Moreover, people may ignore this option outright and get worse performance.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
