[jira] [Comment Edited] (OAK-4805) Misconfigured lucene index definition can render the whole system unusable

["Vikas Saurabh (JIRA)" <ji...@apache.org>]

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

Vikas Saurabh edited comment on OAK-4805 at 9/14/16 10:01 PM:
--------------------------------------------------------------

[~chetanm], can you please take a look at [^OAK-4805.patch] if it's the right place to catch and log the exception. I've not update {{LuceneIndex.java}} though (wasn't sure if we want to maintain that or not).


was (Author: catholicon):
[~chetanm], can you please take a look if it's the right place to catch and log the exception. I've not update {{LuceneIndex.java}} though (wasn't sure if we want to maintain that or not).

> 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, candidate_oak_1_2, candidate_oak_1_4
>             Fix For: 1.6
>
>         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
(v6.3.4#6332)