jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Parvulescu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-2050) Query engine: disable or restrict built-in full-text engine
Date Wed, 27 Aug 2014 08:56:57 GMT

     [ https://issues.apache.org/jira/browse/OAK-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alex Parvulescu updated OAK-2050:
---------------------------------

    Description: 
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.

> 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
>         Environment: 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.
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>             Fix For: 1.1
>
>
> 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.2#6252)

Mime
View raw message