[
https://issues.apache.org/jira/browse/JCR-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545826
]
Jukka Zitting commented on JCR-1237:
------------------------------------
I was about to vote -1 on this, but then I realized that the JCR spec doesn't
actually require document order as the default ordering, it's just an optional
default.
So +0, as this seems useful even though it does mean that a client would need
to use some yet to be implemented custom extension to request document ordering
on a workspace with this default configuration.
Also, we would need to change the QUERY_XPATH_DOC_ORDER repository descriptor
to false. As a somewhat questionable side effect, this change would allow us to
resolve JCR-591 and perhaps even JCR-392 as Won't Fix.
> 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.
