You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Anton Vinogradov (JIRA)" <ji...@apache.org> on 2017/09/05 15:19:00 UTC

[jira] [Comment Edited] (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=16153826#comment-16153826 ] 

Anton Vinogradov edited comment on IGNITE-5468 at 9/5/17 3:18 PM:
------------------------------------------------------------------

[~yzhdanov],
Please review changes in case issue still actual.


was (Author: avinogradov):
[~yzhdanov],
Please review task in case it actual.

> 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: Task
>          Components: sql
>    Affects Versions: 2.0
>            Reporter: Yakov Zhdanov
>            Assignee: Vitaliy Biryukov
>            Priority: Critical
>
> 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)