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 2022/08/10 09:21:00 UTC

[jira] [Updated] (IGNITE-17504) Replace ScanQueryFallbackIterator with GridCacheDistributedQueryFuture

     [ https://issues.apache.org/jira/browse/IGNITE-17504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maksim Timonin updated IGNITE-17504:
------------------------------------
    Summary: Replace ScanQueryFallbackIterator with GridCacheDistributedQueryFuture  (was: Replace ScanFallbackIterator with GridCacheDistributedQueryFuture)

> Replace ScanQueryFallbackIterator with GridCacheDistributedQueryFuture
> ----------------------------------------------------------------------
>
>                 Key: IGNITE-17504
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17504
>             Project: Ignite
>          Issue Type: New Feature
>            Reporter: Maksim Timonin
>            Assignee: Maksim Timonin
>            Priority: Major
>
> Currently, for ScanQuery we have separate branch of query processing - ScanQueryFallbackIterator. That is useful for partitioned request (ScanQuery.setPartition).
> This branch can be re-used with IndexQuery, but firstly it's required to merge this branch with main logic of processing, implemented in GridCacheDistributedQueryFuture.
> Looks like it pretty easy to implement with existing set of fields and methods within this future.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)