You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maksim Timonin (Jira)" <ji...@apache.org> on 2021/10/03 12:42:00 UTC
[jira] [Commented] (IGNITE-15621) Flaky test
MultifieldIndexQueryTest.testCheckBoundaries
[ https://issues.apache.org/jira/browse/IGNITE-15621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17423660#comment-17423660 ]
Maksim Timonin commented on IGNITE-15621:
-----------------------------------------
ATOMIC + PRIMARY_SYNC does not provides guarantees for index writing.
Let's make tests for IndexQuery using transactional cache instead, and create a ticket for discovering atomic behaviour.
> Flaky test MultifieldIndexQueryTest.testCheckBoundaries
> -------------------------------------------------------
>
> Key: IGNITE-15621
> URL: https://issues.apache.org/jira/browse/IGNITE-15621
> Project: Ignite
> Issue Type: New Feature
> Reporter: Maksim Timonin
> Assignee: Maksim Timonin
> Priority: Major
> Labels: IEP-71
>
> Params: nodesCnt=2, qryIdx=null
> Failed line: assertEquals(2, result.size());
> It expect 2 but get 3. Looks like some miss of condition, we check inline in moment of put is writing this inline (so first field is OK, and second is not ready yet)
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)