You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Vikas Saurabh (JIRA)" <ji...@apache.org> on 2016/01/07 15:59:39 UTC

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

     [ https://issues.apache.org/jira/browse/OAK-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vikas Saurabh resolved OAK-3838.
--------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.4)
                   1.3.14

Thanks Thomas for the review. Have committed to trunk at [r1723565|http://svn.apache.org/r1723565]. Resolving the issue.

> 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.3.14
>
>         Attachments: OAK-3838-take2.patch, 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)