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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2016/03/02 08:57:18 UTC

[jira] [Comment Edited] (OAK-2679) Query engine: faster cost calculation

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

Chetan Mehrotra edited comment on OAK-2679 at 3/2/16 7:56 AM:
--------------------------------------------------------------

Note for self - For backporting also include OAK-3480


was (Author: chetanm):
For backporting also include OAK-3480

> Query engine: faster cost calculation
> -------------------------------------
>
>                 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
>              Labels: candidate_oak_1_2, performance
>             Fix For: 1.3.7
>
>         Attachments: 0001-OAK-2679-Reduce-execution-plan-overhead_0.2.patch, OAK-2679-2.patch, OAK-2679.patch, executionplancache.patch
>
>
> 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)