You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Thomas Mueller (JIRA)" <ji...@apache.org> on 2015/03/25 15:52:53 UTC

[jira] [Commented] (OAK-2679) Query engine: cache execution plans

    [ https://issues.apache.org/jira/browse/OAK-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14379993#comment-14379993 ] 

Thomas Mueller commented on OAK-2679:
-------------------------------------

The property index currently only returns the cost, and executing the query will _again_ iterate over all property index nodes. This can be improved as well, if the property index returns the plan.

> Query engine: cache execution plans
> -----------------------------------
>
>                 Key: OAK-2679
>                 URL: https://issues.apache.org/jira/browse/OAK-2679
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, query
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>             Fix For: 1.3.0
>
>
> If there are many indexes, preparing a query can take a long time, in relation to executing the query.
> The query execution plans can be cached. The cache should be invalidated if there are new indexes, or indexes are changed; a simple solution might be to use a timeout, and / or a manual cache clean via JMX or so.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)