Re: IGNITE-5468 ticket description looks confusing.

2017-07-05 Thread Yakov Zhdanov
Let me review when I am back next week. -- Yakov Zhdanov

Re: IGNITE-5468 ticket description looks confusing.

2017-07-05 Thread Andrey Mashenkov
Yes, Yakov. I mean query with join of 2 caches can be run on either of it. Second parameter is merge prefetch size. You can see they going together in PR. 5 июля 2017 г. 11:48 пользователь "Yakov Zhdanov" написал: > Same query against different caches? This sounds like same query against > diff

Re: IGNITE-5468 ticket description looks confusing.

2017-07-05 Thread Yakov Zhdanov
Same query against different caches? This sounds like same query against different tables. :) Andrey can you please provide real-world example? What 2 params do you mean? Which one is the second? My points are: - provide ability to set limits without restarting the cluster. - provide ability to s

Re: IGNITE-5468 ticket description looks confusing.

2017-07-04 Thread Dmitriy Setrakyan
> View this message in context: http://apache-ignite- > developers.2346864.n4.nabble.com/IGNITE-5468-ticket- > description-looks-confusing-tp19436p19438.html > Sent from the Apache Ignite Developers mailing list archive at Nabble.com. >

Re: IGNITE-5468 ticket description looks confusing.

2017-07-04 Thread Vitaliy Biryukov
ese points, I need to add these 2 parameters into Query class. -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-5468-ticket-description-looks-confusing-tp19436p19438.html Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

IGNITE-5468 ticket description looks confusing.

2017-07-04 Thread Andrey Mashenkov
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 paramete