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 2014/02/11 15:04:19 UTC

[jira] [Resolved] (OAK-1395) Automatically cancel long running queries

     [ https://issues.apache.org/jira/browse/OAK-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Mueller resolved OAK-1395.
---------------------------------

    Resolution: Fixed

Revision 1567126 (implementation) and revision 1567132 (documentation).

> Automatically cancel long running queries
> -----------------------------------------
>
>                 Key: OAK-1395
>                 URL: https://issues.apache.org/jira/browse/OAK-1395
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: query
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>             Fix For: 0.17
>
>
> Queries potentially read many nodes, for example because they don't use an index or because they use join conditions that return many nodes.
> Such cases are sometimes not detected early because the default storage engine (the Tar storage) is fast. However it is a problem for slower storage engine (that stores data remotely).
> To detect such cases early on, we could add a limit on how many nodes a query may read. It might make sense to use multiple distinct limits: one for how many nodes were read but skipped, and another limit for how many nodes were read, and a third for how many nodes are kept in memory (for example for "order by" queries).



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)