[
https://issues.apache.org/jira/browse/OAK-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Hirrle updated OAK-2544:
--------------------------------
Description:
With XPATH and SQL(1) it is possible in JCR to use the respect document order
(http://wiki.apache.org/jackrabbit/Search#line-33) to order results how the
content is stored. With SQL2 this issn't possible.
Now all queries are transformed as SQL2 -Queries so you have no chance to do a
query and order it by the structure.
In a CMS content is often stored by the importance (e.g. navigation elements),
so I think a tree based repository should support this feature.
was:
With XPATH and SQL(1) it is possible in JCR to use the respect document order
(http://wiki.apache.org/jackrabbit/Search#line-33) to order results how the
content is stored. With SQL2 this issn't possible.
Now all queries are transformed as SQL2 -Query so you have no chance to do a
query and order it by the structure.
In a CMS content is often stored by the importance (e.g. navigation elements),
so I think a tree based repository should support this feature.
> Respect Document Order does not work anymore
> ---------------------------------------------
>
> Key: OAK-2544
> URL: https://issues.apache.org/jira/browse/OAK-2544
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: oak-lucene
> Reporter: Nicolas Hirrle
>
> With XPATH and SQL(1) it is possible in JCR to use the respect document order
> (http://wiki.apache.org/jackrabbit/Search#line-33) to order results how the
> content is stored. With SQL2 this issn't possible.
> Now all queries are transformed as SQL2 -Queries so you have no chance to do
> a query and order it by the structure.
> In a CMS content is often stored by the importance (e.g. navigation
> elements), so I think a tree based repository should support this feature.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
