[ https://issues.apache.org/jira/browse/IGNITE-12905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17091409#comment-17091409 ]
Johnny Galatikitis commented on IGNITE-12905: --------------------------------------------- [~cyberdemon] great! Is there anything else I should do? Workflow wise > QueryKeyValueIterable missing custom spliterator() implementation > ----------------------------------------------------------------- > > Key: IGNITE-12905 > URL: https://issues.apache.org/jira/browse/IGNITE-12905 > Project: Ignite > Issue Type: Bug > Components: cache, general > Affects Versions: 2.8 > Environment: Windows 10 > JDK 1.8.0_172 > ignite-core 2.8.0 > reactor-core 3.3.3 > Reporter: Johnny Galatikitis > Assignee: Johnny Galatikitis > Priority: Critical > Fix For: 2.8.1 > > Attachments: > IGNITE-12905_-_add_QueryKeyValueSpliterator_and_corresponding_test.patch > > Time Spent: 4h 40m > Remaining Estimate: 0h > > We are using apache ignite with reactor-core and since reactors upgrade from > 3.2.12 to 3.3.3 {code:java} > org.apache.ignite.internal.processors.query.QueryKeyValueIterable.iterator > {code} > is called multiple times. It starts with: > 1. calling iterable.spliterator().hasCharacteristics(Spliterator.SIZED), > where iterable is instanceof QueryKeyValueIterable > 2. calls default implementation > Spliterators.spliteratorUnknownSize(iterator(), 0) > 3. which in turn calls ignite's QueryKeyValueIterable.iterator() call and > that "uses it up" for subsequent calls, i.e. throw IgniteException "Iterator > is already fetched or query was cancelled." -- This message was sent by Atlassian Jira (v8.3.4#803005)