[
https://issues.apache.org/jira/browse/IGNITE-12291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17025211#comment-17025211
]
Yuriy Shuliha commented on IGNITE-12291:
-----------------------------------------
[~Pavlukhin] you are right with the question. As per ordered nature of
TextQuery via Lucene, the client should receive responses from all node in
order to merge results and sort them correctly.
The query with limit works as this: for limit 1000 we must receive at least
1000 entries from every node, merge and sort them. This is the only correct way
it can be implemented using existing distributed queries mechanism.
So this ticked seems to be obsolete and should be dismissed.
> 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: Yuriy Shuliha
> Priority: Major
>
> 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)
