jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vikas Saurabh (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-3838) IndexPlanner incorrectly lets all full text indices to participate for suggest/spellcheck queries
Date Wed, 06 Jan 2016 20:14:39 GMT

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

Vikas Saurabh updated OAK-3838:
-------------------------------
    Attachment: OAK-3838-take2.patch

Attaching [^OAK-3838-take2.patch] which is derivative of the earlier one. Have incorporated
suggestions given by [~chetanm]. Also, have added {{getNodeTypeName}} in {{Filter}} and use
that from IndexPlanner instead (assuming, that's how we decide to get queried node type to
planner)

> 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-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)

Mime
View raw message