[jira] [Commented] (OAK-3838) IndexPlanner incorrectly lets all full text indices to participate for suggest/spellcheck queries

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

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

Vikas Saurabh commented on OAK-3838:
------------------------------------

Have committed the patch in trunk at [r1723142|http://svn.apache.org/r1723142]. Not resolving the issue yet though.

> IndexPlanner incorrectly lets all full text indices to participate for suggest/spellcheck queries
> -------------------------------------------------------------------------------------------------
>
>                 Key: OAK-3838
>                 URL: https://issues.apache.org/jira/browse/OAK-3838
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: lucene
>            Reporter: Vikas Saurabh
>            Assignee: Vikas Saurabh
>             Fix For: 1.4
>
>         Attachments: OAK-3838.patch
>
>
> Currently, index planner builds plan for suggest/spellcheck queries even if the indices don't have those functionality enabled.
> Also, there's another issue: when suggestion/spell-check come into play, we need to dis-allow inheritance behavior of indexingRule. To clarify, a query like {{SELECT [rep:suggest()] from [nt:unstructured] where suggest('test')}} if using some index preparing suggestions on {{nt:base}} would give incorrect suggestions as the index would have suggested values from other type of nodes as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)