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 "Georg Henzler (Jira)" <ji...@apache.org> on 2020/07/01 15:50:00 UTC

[jira] [Commented] (OAK-5291) Per-Query Limits (nodes read, nodes read in memory)

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

Georg Henzler commented on OAK-5291:
------------------------------------

Related discussion from 2019: https://www.mail-archive.com/oak-dev@jackrabbit.apache.org/msg15602.html

Thanks for considering the query option now, I have at least two use cases where this would be very useful to have.

> Per-Query Limits (nodes read, nodes read in memory)
> ---------------------------------------------------
>
>                 Key: OAK-5291
>                 URL: https://issues.apache.org/jira/browse/OAK-5291
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: query
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>            Priority: Major
>             Fix For: 1.32.0
>
>
> In OAK-1395 we added limits for long running queries. In OAK-1571 we added OSGi configuration. In OAK-5237 we change the default settings.
> It would be nice to be able to define the limits per query, similar to OAK-4888. The query would look like (for example, to limit reading to 1 million nodes, even if the default query limit is lower):
> {noformat}
> select * from [nt:base] 
> where ischildnode('/oak:index') 
> order by name()
> option(traversal ok, limit 1000000)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)