Vikas Saurabh edited comment on OAK-4805 at 9/21/16 6:25 PM:

Fixed in trunk at [r1761762|https://svn.apache.org/r1761762]. Backported to 1.4 
at [r1761768|https://svn.apache.org/r1761768] and 1.2 at 

Fixed broken test ({{LuceneIndexTest#indexNodeLockHandling}}) at 
[r1761787|https://svn.apache.org/r1761787] on trunk, at 
[r1761791|https://svn.apache.org/r1761791] on 1.4 and at 
[r1761792|https://svn.apache.org/r1761792] on 1.2. I had run the tests with 
{{IllegalArgumentException}} and assumed that generalizing to {{Exception}} was 
ok... sorry for the noise :-(.

was (Author: catholicon):
Fixed in trunk at [r1761762|https://svn.apache.org/r1761762]. Backported to 1.4 
at [r1761768|https://svn.apache.org/r1761768] and 1.2 at 

> 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