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 "Amit Jain (JIRA)" <ji...@apache.org> on 2016/05/10 04:21:12 UTC

[jira] [Updated] (OAK-2618) Improve performance of queries with ORDER BY and multiple OR filters

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

Amit Jain updated OAK-2618:
---------------------------
    Fix Version/s: 1.2.15

> Improve performance of queries with ORDER BY and multiple OR filters
> --------------------------------------------------------------------
>
>                 Key: OAK-2618
>                 URL: https://issues.apache.org/jira/browse/OAK-2618
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: query
>            Reporter: Amit Jain
>            Assignee: Amit Jain
>              Labels: performance
>             Fix For: 1.3.1, 1.4, 1.2.15
>
>
> When multiple OR constraints are specified in the XPATH query, itis broken up into union of multiple clauses. If query includes an order by clause, the sorting in this case is done by traversing the result set in memory leading to slow query performance.
> Possible improvements could include:
> * For indexes which can support multiple filters (like lucene, solr) such queries should be efficient and the query engine can pass-thru the query as is.
> ** Possibly also needed for other cases also. So, we can have some sort of capability advertiser for indexes which can hint the query engine 
> and/or
> * Batched merging of the sorted iterators returned for the multiple union queries (possible externally).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)