Ivan Pavlukhin commented on IGNITE-12401:

[~Yuriy_Shuliha], [~ilyak], I dig into the problem and found that the cause of 
the test failure is improper mapping of text queries on topology when there are 
MOVING partitions.
The scenario in test is as follows:
1. Start 2 nodes.
2. Fill cache with data.
3. Execute text query and check results.

And the tricky thing here is that between steps 1 and 2 there are MOVING 
partitions! Really misleading, because it seems that there should be no data 
movement as cluster starts without data, but the reality is different. As a 
result text query loads some entries twice (from both nodes).

So, we identified that _mapping_ of text queries on topology works incorrectly. 
Consequently incorrect results on topologies with MOVING partitions.

> Some Text Queries return repeated results
> -----------------------------------------
>                 Key: IGNITE-12401
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12401
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 2.8
>            Reporter: Ilya Kasnacheev
>            Assignee: Yuriy Shuliha 
>            Priority: Critical
>          Time Spent: 10m
>  Remaining Estimate: 0h
> It came to my attention while checking for Range Queries support that we 
> don't actually check that found query results are the correct ones.
> We were checking that we got some results, but not whether they were expected.
> And voila, it turns out that Range Queries examples, as well as some other 
> test cases, will readily fail when run with such checks! A query will return 
> same value repeatedly, e.g. range query will return the "1" record twice, and 
> limited text query will return "14" record twice.
> It didn't really occur on non-range queries before the introduction of limits.
> I think we should not ship broken limit queries. Maybe also fix range 
> queries, if it's hard let's @Ignore them for now.

This message was sent by Atlassian Jira

Reply via email to