[
https://issues.apache.org/jira/browse/OAK-9376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17298870#comment-17298870
]
Thomas Mueller commented on OAK-9376:
-------------------------------------
We already have ["LimitInMemory" and
"LimitReads"|http://jackrabbit.apache.org/oak/docs/query/query-engine.html#Slow_Queries_and_Read_Limits].
Those are global options (are used for all queries). This might already be
sufficient for your case?
It would make sense to have stricter limits per query... That would require a
change. For example, you can set the global limit LimitInMemory = 100'000, and
the option per query to 10'000. The syntax for this could be "option(limit
memory 10000)" or "option(limit reads 20000)" or "option(limit memory 10000,
limit reads 20000)".
> 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)
