You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2018/08/01 06:22:19 UTC

[jira] [Commented] (IGNITE-584) Need to make sure that scan query returns consistent results on topology changes

    [ https://issues.apache.org/jira/browse/IGNITE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564788#comment-16564788 ] 

Semen Boikov commented on IGNITE-584:
-------------------------------------

Reviewed, changes look ok (don't forget before merge remove this from StripedExecutor: {color:#808080}//System.err.println("runnable: " + cmd)
{color}

> Need to make sure that scan query returns consistent results on topology changes
> --------------------------------------------------------------------------------
>
>                 Key: IGNITE-584
>                 URL: https://issues.apache.org/jira/browse/IGNITE-584
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: data structures
>    Affects Versions: 1.9, 2.0, 2.1
>            Reporter: Artem Shutak
>            Assignee: Stanilovsky Evgeny
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain, Muted_test
>             Fix For: 2.7
>
>         Attachments: tc1.png
>
>
> Consistent results on topology changes was implemented for sql queries, but looks like it still does not work for scan queries.
> This affects 'cache set' tests since set uses scan query for set iteration (to be unmuted on TC): 
> GridCacheSetAbstractSelfTest testNodeJoinsAndLeaves and testNodeJoinsAndLeavesCollocated; 
> Also see todos here GridCacheSetFailoverAbstractSelfTest



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)