You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Biryukov Vitaliy (JIRA)" <ji...@apache.org> on 2017/06/26 12:50:00 UTC
[jira] [Commented] (IGNITE-5468) Need to set
IGNITE_SQL_MERGE_TABLE_MAX_SIZE on per query basis
[ https://issues.apache.org/jira/browse/IGNITE-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063039#comment-16063039 ]
Biryukov Vitaliy commented on IGNITE-5468:
------------------------------------------
I also added the ability to set IGNITE_SQL_MERGE_TABLE_PREFETCH_SIZE, because it is coupled with IGNITE_SQL_MERGE_TABLE_MAX_SIZE.
And I left the opportunity to configure these parameters using system properties. System properties will be used as default cache properties and for queries without strict dependency on concrete cache.
> 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)