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 "Thomas Mueller (JIRA)" <ji...@apache.org> on 2014/08/04 12:29:13 UTC

[jira] [Closed] (OAK-1999) Query engine is slow when using many "or" constraints

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

Thomas Mueller closed OAK-1999.
-------------------------------


> Query engine is slow when using many "or" constraints
> -----------------------------------------------------
>
>                 Key: OAK-1999
>                 URL: https://issues.apache.org/jira/browse/OAK-1999
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: query
>    Affects Versions: 1.0, 1.0.1, 1.0.2
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>             Fix For: 1.1, 1.0.4
>
>
> For queries with many (300 or so) "or" constraints of the form "x = 1 or x = 2 or x = 3", the query engine uses quite a lot of CPU time. According to profiling data, this is due to using "toString()" too often, and "Sets.union" (com.google.common.collect.Sets).
> The Oak 1.0 branch is affected most, not sure about trunk.



--
This message was sent by Atlassian JIRA
(v6.2#6252)