Denis,
It appears that in current implementation the page size means number of
rows which will be sent in a single message between nodes but it does not
define how many pages will be loaded. I agree that it is kind of unexpected
behavior but this is not that easy to fix.
We need to add lazy mode t
Good,
Sergi I've merged the test to 1.4 branch and assigned IGNITE-613 on you.
When you fix the issue please validate the fix with this test and unmute
the test by removing 'fail(...)' statement at the beginning of its body.
--
Denis
On 9/10/2015 4:00 PM, Sergi Vladykin wrote:
Something li
Something like this could happen because replicated cache is incorrectly
expected to have the whole dataset locally.
I will take a look .
Sergi
2015-09-10 15:38 GMT+03:00 Denis Magda :
> Hi Sergi,
>
> I was fixing one of the many SQL query tests (
> https://issues.apache.org/jira/browse/IGNITE-6
Hi Sergi,
I was fixing one of the many SQL query tests
(https://issues.apache.org/jira/browse/IGNITE-613) when found that there
is an issue in how 'pageSize' parameter is processed by Ignite SQL engine.
Test does the following.
At the beginning it starts 3 server nodes and 1 client node. Fil
