[
https://issues.apache.org/jira/browse/OAK-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13915844#comment-13915844
]
Alex Parvulescu commented on OAK-1263:
--------------------------------------
good stuff!
I took a quick look at the pull request in github and noticed there's an
impressive amount of code formatting that doesn't really need to be there.
Could you please apply the same formatting rules as before? It makes applying
the patch 10x faster.
Another note: some files are missing Apache licence headers, as can be seen
from the failing travis build on you pull-request [0] under "Too many files
with unapproved license: 3 See RAT report in:
/home/travis/build/apache/jackrabbit-oak/oak-core/target/rat.txt".
Yes, travis will automatically run the tests on your clone too, and send the
result to the oak-dev list, that's how cool it is :)
[0] https://travis-ci.org/apache/jackrabbit-oak/builds/19806445
> optimize oak index to support 'fast ORDER BY' queries to support sorting &
> pagination for large set of children
> ---------------------------------------------------------------------------------------------------------------
>
> Key: OAK-1263
> URL: https://issues.apache.org/jira/browse/OAK-1263
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
> Affects Versions: 0.12
> Reporter: Stefan Egli
> Assignee: Alex Parvulescu
> Fix For: 0.18
>
> Attachments: OAK-1263-r1.patch, benchmark-20140228112150.log,
> benchmark-20140228120718.log, benchmark-20140228125248.log
>
>
> We have a use case where we'd like to be able to use an index in a
> "pagination-like" fashion. That is, we'd like to be able to have an index on
> a subtree on a certain property, and then run a query which does ORDER BY
> that property combined with OFFSET. That way, essentially allowing pagination
> of child nodes of a particular parent based on 'sorted by a certain property'.
> AFAIU currently the oak index is not optimized to support ORDER BY queries in
> a fast manner. The index keeps 'the child nodes unsorted', ie to process an
> ORDER BY, the child nodes would have to be 'manually sorted' which can result
> in bad performance given a large number of child nodes.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
