[
https://issues.apache.org/jira/browse/JCR-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545838
]
Marcel Reutegger commented on JCR-1237:
---------------------------------------
Hmm, I completely forgot about the repository descriptor. This is currently
hard coded in a properties file. With Jackrabbit it is actually possible to
have document order on results in one workspace but not in another one. Which
raises an interesting question. What does QUERY_XPATH_DOC_ORDER return in that
case?
Jackrabbit should probably enable or disable document order on all workspaces
and not selectively.
Jukka wrote:
> it does mean that a client would need to use some yet to be implemented
> custom extension
my intention was to provide a default configuration where you won't have
document order, but if you wish the repository to do so you could enable it in
the configuration.
> Change default value for respectDocumentOrder
> ---------------------------------------------
>
> Key: JCR-1237
> URL: https://issues.apache.org/jira/browse/JCR-1237
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Marcel Reutegger
> Priority: Minor
>
> The current default value for the search index configuration parameter
> respectDocumentOrder is true. Almost all applications are not interested in
> document order, while this default adds significant overhead to query
> execution because document order information is present in the index but has
> to be calculated over the complete result set.
> I propose to change the default value to false and document this change in
> the 1.4 release notes. If an application relies on document order one can
> still explicitly set the parameter in the configuration to true.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
