[
https://issues.apache.org/jira/browse/IGNITE-12291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17022948#comment-17022948
]
Ivan Pavlukhin commented on IGNITE-12291:
-----------------------------------------
[~Yuriy_Shuliha], what problem should this ticket primarily solve? Let me
describe my understanding on example. Correct me if I am getting something
wrong. An example:
_A query with a limit 1000. With current implementation we must receive 1000
entries from every node before finishing query. With NextPageRequest (e.g. page
size is 100) we will be able to stop processing as long as we received 1000
entries which fit our needs._
> 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)
