[
https://issues.apache.org/jira/browse/OAK-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14249729#comment-14249729
]
Przemo Pakulski edited comment on OAK-2056 at 12/17/14 11:31 AM:
-----------------------------------------------------------------
I can confirm, It helped with my queries as well. Ordering timings by date
fields are now comparable to other types (e.g. strings).
Any chance to include it in upcoming release ?
was (Author: ppakulski):
I can confirm, It helped with my queries as well. Ordering timings by date
fields are now comparable to other tpes (e.g. strings)
> Optimize orderings by date fields
> ---------------------------------
>
> Key: OAK-2056
> URL: https://issues.apache.org/jira/browse/OAK-2056
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
> Affects Versions: 1.0.4, 1.0.8
> Reporter: Przemo Pakulski
> Assignee: Davide Giannella
> Labels: performance
> Attachments: OAK-2056-r1.patch
>
>
> Sorting by date fields is very slow in oak, especially if result set size is
> large.
> I'm running the following JCR-SQL2 query
> {code}
> SELECT * FROM [cq:PageContent] AS [c] WHERE ISDESCENDANTNODE('/content')
> {code}
> which returns 3270 results on my oak repo.
> {noformat}
> Query execution times are as below
> ---------------------------------------
> No order clause | 0,147 sec
> ORDER BY [jcr:title] | 1,203 sec
> ORDER BY [jcr:createdBy] | 1,018 sec
> ORDER BY [jcr:created] | 25,229 sec
> {noformat}
> Ordering by date field adds extra 24 seconds overhead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
