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] [Created] (OAK-8294) Make it possible to mark a (customer) query as bad and skip it
Date Fri, 03 May 2019 08:40:00 GMT
Thomas Mueller created OAK-8294:
-----------------------------------

             Summary: Make it possible to mark a (customer) query as bad and skip it
                 Key: OAK-8294
                 URL: https://issues.apache.org/jira/browse/OAK-8294
             Project: Jackrabbit Oak
          Issue Type: New Feature
          Components: query
            Reporter: Thomas Mueller
            Assignee: Thomas Mueller


Application code can run all kinds of bad queries (reading a lot of data, slow, high memory
usage).

The best solution is to fix the application of course. But that can take a while, and until
this is done, it would be good if bad queries can be blocked in another way. Problematic queries
would either just log a warning, or be blocked (throw an exception when trying to run).

Blocking should be possible via JMX, but also via persistent configuration (in the repository),
so that a restart remembers which queries are blocked.

I don't think it's needed to stop already running queries, as the traversal limit should solve
this (it can be re-configured at runtime if needed). Also, reading the patterns from the repository
is only needed at startup (while running, JMX can be used to temporarily add patterns).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message