[
https://issues.apache.org/jira/browse/IGNITE-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063046#comment-16063046
]
ASF GitHub Bot commented on IGNITE-5468:
----------------------------------------
GitHub user BiryukovVA opened a pull request:
https://github.com/apache/ignite/pull/2193
IGNITE-5468
IGNITE-5468: Added the ability to set IGNITE_SQL_MERGE_TABLE_MAX_SIZE and
IGNITE_SQL_MERGE_TABLE_PREFETCH_SIZE via cache configuration
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/BiryukovVA/ignite IGNITE-5468
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2193.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2193
----
commit eeb9a4cf5d868c7c2361a7b9b83b0245ee5970c3
Author: Vitaliy <[email protected]>
Date: 2017-06-26T09:37:16Z
IGNITE-5468: Added the ability to set IGNITE_SQL_MERGE_TABLE_MAX_SIZE and
IGNITE_SQL_MERGE_TABLE_PREFETCH_SIZE via cache configuration
commit 6446d085419c140f03511e1867c72069d47b3055
Author: Vitaliy <[email protected]>
Date: 2017-06-26T11:17:10Z
IGNITE-5468: Refactoring.
commit 08734b11c7456aee6292ecc3b0778a8187fe76a4
Author: Vitaliy <[email protected]>
Date: 2017-06-26T09:37:16Z
IGNITE-5468: Added the ability to set IGNITE_SQL_MERGE_TABLE_MAX_SIZE and
IGNITE_SQL_MERGE_TABLE_PREFETCH_SIZE via cache configuration
commit 4a2c75c785c6a7403a0e7b9a05a3b3a07b888e5e
Author: Vitaliy <[email protected]>
Date: 2017-06-26T11:17:10Z
IGNITE-5468: Refactoring.
commit 2aa81f94b31c94efde0ad7d765bd4a70cb486e32
Author: Vitaliy <[email protected]>
Date: 2017-06-26T12:52:21Z
Merge remote-tracking branch 'origin/IGNITE-5468' into IGNITE-5468
----
> Need to set IGNITE_SQL_MERGE_TABLE_MAX_SIZE on per query basis
> --------------------------------------------------------------
>
> Key: IGNITE-5468
> URL: https://issues.apache.org/jira/browse/IGNITE-5468
> Project: Ignite
> Issue Type: Improvement
> Reporter: Yakov Zhdanov
> Assignee: Biryukov Vitaliy
> Priority: Critical
> Fix For: 2.1
>
>
> Currently this property can be set via sys property only thus changing it
> will require restart of the cluster. I think it is better to set it on
> perquery basis with some default that is configured via cache configuration.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
