[
https://issues.apache.org/jira/browse/IGNITE-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16073642#comment-16073642
]
Andrew Mashenkov commented on IGNITE-5468:
------------------------------------------
[~VitaliyB], [~yzhdanov], [~sergi.vladykin]
Looks like, there is no need to pass CacheContext everywhere for each query
just for getting value that will never be changed after cache has been started.
We have to simplify that.
Ticket and solution looks confusing, so I've start a thread on dev list [1].
[1]
http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-5468-ticket-description-looks-confusing-td19436.html
> 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.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)
