Vikas Saurabh commented on OAK-4805:

[~chetanm], I'd like to backport this to 1.0 as well, but in absence of custom 
analyzer feature in 1.0 I don't know how to test a mis-configured index. Ideas?

> Misconfigured lucene index definition can render the whole system unusable
> --------------------------------------------------------------------------
>                 Key: OAK-4805
>                 URL: https://issues.apache.org/jira/browse/OAK-4805
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: lucene
>            Reporter: Vikas Saurabh
>            Assignee: Vikas Saurabh
>              Labels: candidate_oak_1_0
>             Fix For: 1.6, 1.4.8, 1.5.11, 1.2.20
>         Attachments: OAK-4805.patch
> Mis-configured index definition can throw an exception while collecting 
> plans. This causes any query (even unrelated ones) to not work as cost 
> calculation logic would consult a badly constructed index def. Overall a 
> mis-configured index definition can practically grind the whole system to 
> halt as the whole query framework stops working.

This message was sent by Atlassian JIRA

Reply via email to