jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davide Giannella (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (OAK-8294) Make it possible to mark a (customer) query as bad and skip it
Date Tue, 11 Jun 2019 10:52:13 GMT

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

Davide Giannella closed OAK-8294.

bulk close 1.14.0

> 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
>            Priority: Major
>             Fix For: 1.14.0
>         Attachments: OAK-8294.patch, OAK-8294_v2.patch
> 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
> 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

This message was sent by Atlassian JIRA

View raw message