[
https://issues.apache.org/jira/browse/IGNITE-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153909#comment-16153909
]
Yakov Zhdanov commented on IGNITE-5468:
---------------------------------------
[~vozerov], I was on customer side and Ignite failed for query I sent with
error message that merge_table_max_size has been exceeded. If we don't
implement this then the only way to fix this is to restart servers since it is
not changeable at runtime at all.
Ideally, it would be cool to remove this property and do all the merges offheap
and span to disk if necessary. In this case all ad-hoc queries will become
possible without any extra configuration.
Thanks!
> 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)
