[
https://issues.apache.org/jira/browse/JCR-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673856#action_12673856
]
Ard Schrijvers commented on JCR-800:
------------------------------------
Question about the RelPathScoreDocComparator.sortValue(ScoreDoc i) : Will for
every comparison the property value be refetched through the ISM? If so,
temporal storing the result of sortValue might be necessary because this easily
blows up cpu if it is not cached temporarily.
Furthermore, but you already indicate above, i think the sorting by child axis
will currently not scale very well. Perhaps it might be easier to constrain
sorting on child axis only for childnodes that are indexed through aggregates.
Obviously, your solution does not need indexing configuration / re-indexing
after changing so is much more general, but also pretty resource intensive
> Child Axis support in order by clause
> -------------------------------------
>
> Key: JCR-800
> URL: https://issues.apache.org/jira/browse/JCR-800
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core, jackrabbit-spi-commons, xpath
> Reporter: Savvas Triantafyllou
> Fix For: 1.6.0
>
> Attachments: JCR-800-core.patch, JCR-800-spi-commons.patch
>
>
> Hi,
> since child axis is supported in XPath predicates, it would be nice to
> support it in order by clause as well
> Queries of type
> //element(*, type) [ foo/@bar ] order by foo/@bar asc
> can become very useful
> BR,
> Savvas
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
