jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (Jira)" <j...@apache.org>
Subject [jira] [Commented] (OAK-9376) Optionally reject queries with huge result sets
Date Tue, 09 Mar 2021 16:36:00 GMT

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

Thomas Mueller commented on OAK-9376:
-------------------------------------

I'm not sure... We already have "option(traversal fail)" to avoid traversal; we have limits
on maximum number of results (Query.setLimit I think). Setting the maximum memory per query,
in MB, sounds a bit strange, as it would depend on the actual data. Setting the time limit
is also strange, as it would depend on the load of the system.

What I think would make sense is to add "option(limit 10)" as an alternative to Query.setLimit.
And "option(offset 10)" as an alternative to setOffset. That way, it's possible to set them
via query, and no need to use the JCR API. To set both: "option(offset 10, limit 20)".

> Optionally reject queries with huge result sets
> -----------------------------------------------
>
>                 Key: OAK-9376
>                 URL: https://issues.apache.org/jira/browse/OAK-9376
>             Project: Jackrabbit Oak
>          Issue Type: Wish
>          Components: query
>            Reporter: Manfred Baedke
>            Assignee: Manfred Baedke
>            Priority: Minor
>
> In cases where processing a result of a query uses a lot of memory and/or time (e.g.
where filtering or ordering of many nodes in memory is required), an option to set an upper
limit to the number of processed nodes and fail the query if the limit is exceeded would be
useful.



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

Mime
View raw message