[
https://issues.apache.org/jira/browse/OAK-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amit Jain updated OAK-2295:
---------------------------
Attachment: OAK-2295.patch
Proposed patch which takes the option 1 below.
* Ignore sorting in the query engine if {{jcr:score descending}} is specified
but sort in the query engine when {{jcr:score ascending}} is specified. This
looks semantically correct but queries would have to change to {{descending}}
to take advantage of this.
* Ignore both {{jcr:score ascending/descending}} cases. This would not involve
any sorting in the query engine and the results would be returned in descending
order. This will break the semantics a little but any queries with
{{jcr:score}} would not need to change.
[~chetanm], [~tmueller], [~mreutegg]
Please review and what is your opinion on the options above?
> Using "order by jcr:score" slows down queries by a few orders of magnitude
> --------------------------------------------------------------------------
>
> Key: OAK-2295
> URL: https://issues.apache.org/jira/browse/OAK-2295
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: oak-lucene
> Affects Versions: 1.0.8
> Environment: Linux 2.6.32-431.23.3.el6.x86_64 VM,
> 16GB RAM
> 4 Core Intel(R) Xeon(R) CPU E5-4640 0 @ 2.40GHz
> Reporter: Punyanjan Sen
> Priority: Critical
> Attachments: OAK-2295.patch
>
>
> The following query takes over 16 seconds to run on our QA system:
> /jcr:root/content/help/en//*[jcr:contains(., 'illustrator')] order by
> jcr:score
> Removing the "order by jcr:score" reduces the query time to 14ms
> The time taken increases linearly with the amount of content in our
> repository.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
