[
https://issues.apache.org/jira/browse/OAK-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948637#comment-14948637
]
Thomas Mueller edited comment on OAK-3495 at 10/8/15 1:24 PM:
--------------------------------------------------------------
[~alex.parvulescu] and [~edivad], could you please review the above patch? It
is really just to prevent OOME. First I thought we should also disable the
built-in engine, but now I see it would require more changes. The above code
should match the Oak 1.2 and newer behavior _if_ the built-in engine would be
enabled there, _and_ no (Lucene or Solr) index is available. This is the case
for some of the unit tests, and (for a very short time) just after creating a
new Oak repository, at the very first startup.
was (Author: tmueller):
[~alex.parvulescu] and [~edivad], could you please review the above patch? It
is really just to prevent OOME. First I thought we should also disable the
built-in engine, but now I see it would require more changes. The above code
should match the Oak 1.2 and newer behavior _if_ the built-in engine would be
enabled there. This is the case for some of the unit tests.
> Query engine: disable or restrict built-in full-text engine (backport to 1.0)
> -----------------------------------------------------------------------------
>
> Key: OAK-3495
> URL: https://issues.apache.org/jira/browse/OAK-3495
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Fix For: 1.0.23
>
>
> With Oak 1.0.x, the built-in full-text engine is used if no other full-text
> index is available. This is different than in newer versions of Oak, where
> the built-in engine is disabled in that case by default.
> I think it makes sense to backport this to Oak 1.0.x, so that all versions
> behave the same way.
> This is to prevent out-of-memory problems if no full-text index is configured.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
