ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vitaliy Biryukov (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-5468) Need to set IGNITE_SQL_MERGE_TABLE_MAX_SIZE on per query basis
Date Tue, 11 Jul 2017 09:58:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16081984#comment-16081984
] 

Vitaliy Biryukov  edited comment on IGNITE-5468 at 7/11/17 9:57 AM:
--------------------------------------------------------------------

The thread was started on nabble:
http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-5468-ticket-description-looks-confusing-tt19436.html

[~yzhdanov], please take a look.
Is my implementation correct?


was (Author: vitaliyb):
The thread was started on nabble:
http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-5468-ticket-description-looks-confusing-tt19436.html

[~yzhdanov], please take a look?
Is my implementation correct?

> 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
>    Affects Versions: 2.0
>            Reporter: Yakov Zhdanov
>            Assignee: Vitaliy Biryukov 
>            Priority: Critical
>             Fix For: 2.2
>
>
> 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)

Mime
View raw message