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

Thomas Mueller commented on OAK-8294:
-------------------------------------

Example query validator json:

{noformat}
QueryValidatorJson      (pretty printed):
[
  {
    "key": "helloWorld",
    "pattern": ".*Hello World.*",
    "comment": "HelloTest",
    "failQuery": true,
    "executedLast": "2019-05-03 10:30:25.279",
    "executedCount": 1
  },
  {
    "key": "test",
    "pattern": "testQuery",
    "comment": "",
    "failQuery": true,
    "executedLast": "2019-05-03 10:30:47.612",
    "executedCount": 1
  }
]
{noformat}

{noformat}
http://localhost:4502/oak:index/queryValidator.tidy.-1.json
{
  "jcr:primaryType": "nt:unstructured",
  "helloWorld": {
    "jcr:primaryType": "nt:unstructured",
    "pattern": ".*Hello World.*",
    "failQuery": true,
    "comment": "HelloTest"
    }
  }
{noformat}


> 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
>         Attachments: OAK-8294.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 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)

Reply via email to