[
https://issues.apache.org/jira/browse/OAK-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14112058#comment-14112058
]
Alex Parvulescu commented on OAK-2050:
--------------------------------------
One of the issue with the way FullTextSearchImpl works is that the
FullTextSearchImpl will call #getValue(STRING) on a property without checking
the type first, and if that's an _external binary_ then there's trouble for the
SegmentMK, you'll get a cryptic error:
bq. java.lang.IllegalStateException: String is too long: 2318847354967717297
The code needs to take into account the impact of reading binaries as strings.
> 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
> 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)
