[
https://issues.apache.org/jira/browse/IGNITE-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152444#comment-16152444
]
Vladimir Ozerov commented on IGNITE-5468:
-----------------------------------------
[~yzhdanov], [~amashenkov], [~daradurvs], [~VitaliyB],
Folks, what is the rationale behind this change? I've never saw a single
practical case when it was required to tune this very subtle property on
per-query basis. Suppose that we added it. How user is going to understand when
and how to tune it?
I vote for closing this as won't fix. Too little value, too difficult to
understand.
> 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)
