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

Maksim Timonin commented on IGNITE-12291:
-----------------------------------------

Hi [~amashenkov]!

Currently there are void GridCacheQueryRequests, that filled on nodes and 
skipped on query node due to limit. This patch fixes that: after query exceeds 
limit it sends a cancel query to other nodes instead of multiple page requests 
(with GridCacheQueryRequest). So we win some time on transferring useless data 
between nodes.

As I see SQL queries works the same way. It prepares all data on first 
onQueryRequest and NextPageRequests just iterates over existing collection of 
ResultSet.

P.S. we lose info about score in return iterator of GridLuceneIndex, because 
TextQuery returns cache pairs <K ,V> from every node, without score.

> Create controllable paged query requests / responses for TextQuery similar to 
> current SQL result processing
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-12291
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12291
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Yuriy Shuliha 
>            Assignee: Maksim Timonin
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> For now query initiator node sends 1 _GridCacheQueryRequest_ and can get 
> multiple _GridCacheQueryResponse_-s per remote.
> TextQuery processing finishes when all remotes send _GridCacheQueryResponse_ 
> with 'finished' flag.
> _TextQuery_ processingĀ  should be reworked like it was done for SQL queries.
> Ignite has _GridQueryNextPageRequest \ Response_ classes for SQL result 
> processing.
> Similar processing should be implemented for _TextQueries_:
> *GridTextQueryNextPageRequest*
> *GridTextQueryNextPageResponse* 
> Proper _TextQuery_ response processing should be implemented inĀ 
> _GridCacheQueryFutureAdapter._
> This will allow us to add correct sorting and apply limit correctly on reduce.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to