You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Manfred Baedke (Jira)" <ji...@apache.org> on 2021/03/04 18:05:00 UTC

[jira] [Commented] (OAK-9374) Lucene: LIKE conditions combined with OR are not passed to Lucene

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

Manfred Baedke commented on OAK-9374:
-------------------------------------

I suspect that the root cause is similar to that of OAK-7109 (multiple conditions combined with OR are never passed to Lucene and the alternative UNION query always loses the cost war).
[~thomasm], [~catholicon], [~ngupta], do you have opinions on this?

> Lucene: LIKE conditions combined with OR are not passed to Lucene
> -----------------------------------------------------------------
>
>                 Key: OAK-9374
>                 URL: https://issues.apache.org/jira/browse/OAK-9374
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: lucene
>            Reporter: Manfred Baedke
>            Priority: Minor
>
> While a single LIKE condition works, combining multiple of them (using the same indexed property) with OR leads to a simple Lucene TermQuery being used with just a not null condition for the property being used. The result is correct, but the performance and memory usage suffer.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)