[
https://issues.apache.org/jira/browse/OAK-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133973#comment-14133973
]
Thomas Mueller commented on OAK-2050:
-------------------------------------
Alex and me discussed this offline and came to the following conclusion: If no
"real" full-text index is available, no results should be returned, and a
warning is written to the log file saying that: either no full-text index is
available, or the index is being re-built. That means the built-in full-text
engine is disabled.
> Query engine: disable or restrict built-in full-text engine
> -----------------------------------------------------------
>
> Key: OAK-2050
> URL: https://issues.apache.org/jira/browse/OAK-2050
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Fix For: 1.1, 1.0.6
>
> Attachments: ExternalBlobTest.java.patch
>
>
> There is a built-in full-text engine that is used for full-text queries if no
> full-text index (Lucene, Solr) is available.
> This built-in engine tries to load binaries in memory, which can result in
> out-of-memory.
> We either need a way to disable this built-in mechanism (in which case the
> query engine would throw an exception for full-text queries), and / or change
> the built-in mechanism so it doesn't result in out-of-memory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
