[jira] [Commented] (OAK-925) Query: Lucene index loads all path in memory

["Thomas Mueller (JIRA)" <ji...@apache.org>]

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

Thomas Mueller commented on OAK-925:
------------------------------------

As far as I understand, this is not currently an issue for the known use cases.

Possibly the best way to solve the problem is to first limit the result to 100 entries, and only if the user iterates over all those 100 entries re-run the Lucene query with a limit of 200 (then 400, then 800, and so on).

Anyway, I don't consider this to be a blocking issue, but maybe I'm wrong.

I don't plan to work on it right now, therefore I un-assign the issue.

> Query: Lucene index loads all path in memory
> --------------------------------------------
>
>                 Key: OAK-925
>                 URL: https://issues.apache.org/jira/browse/OAK-925
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: query
>            Reporter: Thomas Mueller
>             Fix For: 0.16
>
>
> Currently the Lucene index loads all paths in memory.
> This could result in an out-of-memory if there are many results. Also, it slows down performance if we only care about some of the results.
> Instead, the data should be loaded on demand if possible.
> As we anyway refactor the full-text engine, it doesn't make sense to solve this problem right now (with the existing Lucene index implementation), but wait for OAK-902 to be completed.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)