ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuriy Shuliha (Jira)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-12189) Implement correct limit for TextQuery
Date Tue, 22 Oct 2019 11:55:00 GMT

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

Yuriy Shuliha  commented on IGNITE-12189:
-----------------------------------------

'total' and 'limit' merged into single 'totalCnt' int variable
Corresponding unit tests have run successfully.

CC: [~amashenkov]

> Implement correct limit for TextQuery
> -------------------------------------
>
>                 Key: IGNITE-12189
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12189
>             Project: Ignite
>          Issue Type: Improvement
>          Components: general
>            Reporter: Yuriy Shuliha 
>            Assignee: Yuriy Shuliha 
>            Priority: Major
>             Fix For: 2.8
>
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> PROBLEM
> For now each server-node returns all response records to the client-node and it may contain
~thousands, ~hundred thousands records.
>  Event if we need only first 10-100. Again, all the results are added to queue in _*GridCacheQueryFutureAdapter*_
in arbitrary order by pages.
>  There are no any means to deliver deterministic result.
> SOLUTION
>  Implement _*limit*_ as parameter for _*TextQuery*_ and _*GridCacheQueryRequest*_ 
>  It should be passed as limit  parameter in Lucene's  _*IndexSearcher.search()*_ in
_*GridLuceneIndex*_.
> For distributed queries _*limit*_ will also trim response queue when merging results.
> Type: long
>  Special value: : 0 -> No limit (Integer.MAX_VALUE);



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

Mime
View raw message