[
https://issues.apache.org/jira/browse/JCR-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545859
]
Jukka Zitting commented on JCR-1237:
------------------------------------
Marcel:
> What does QUERY_XPATH_DOC_ORDER return in that case?
I think the only really correct result would be for the descriptor to be false
(or actually not to exist in the first place). But given that few (if any)
clients actually use that descriptor for in any real functional sense, one
could argue that the descriptor is more useful as an informational tool to
human operators, in which case making the descriptor reflect the default
setting would also make sense.
We could use the default setting from the Workspace template in repository.xml
to decide the state of the QUERY_XPATH_DOC_ORDER descriptor.
> 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.
The information is still in the query index, isn't it? What should I do if I
have a client that mostly doesn't about document order for most queries, but
occasionally would like to use the ordering within the same workspace?
> 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.
