Guys, We have a ticket that is implemented, but the ticket itseft and the solution looks confusing as ticket title is differs to its description: "IGNITE-5468: Need to set IGNITE_SQL_MERGE_TABLE_MAX_SIZE on per query basis" [1]
Seems, initially, we want to have ability to change these 2 parameters as on per-query basis as its defaults. Having defaults in cache configuration is error prone as we can run same query on different caches with different defaults. With this approach we will get confused if same query will work fine with one cache and fails with OOME on another. Furthermore, we have a plans to move sql configuration options out from cache configuration in future releases. Lets introduce additional options in SqlQuery and SqlFieldsQuery classes and leave CacheConfiguration without changes. Thus, *there will no need to pass cache context to methods and classes increasing code complexity. *end user will have ability to tune every single query. *avoid confusing situation with running same query on different caches. Thoughts? [1] https://issues.apache.org/jira/browse/IGNITE-5468 -- Best regards, Andrey V. Mashenkov
