2 Apr
2014
2 Apr
'14
9:41 a.m.
On Wed, Apr 2, 2014 at 9:53 AM, Marius Dumitru Florea
<mariusdumitru.florea(a)xwiki.com> wrote:
Hi Dmitry,
On Mon, Mar 31, 2014 at 5:33 AM, Dmitry Bakbardin <haru_mamburu(a)mail.ru> wrote:
(3) It was a fake prefix matching, because if you typed more words,
only the last word was matched as prefix (not the entire text). All
the other were analysed.
Hi, all!
5.2 -> 5.4.3 Upgrade
Xwiki.SearchSuggest objects were changed
It was:
type:OBJECT AND (class:XWiki.BlogPostClass) AND objcontent:(__INPUT__*)
It is:
fq=type:DOCUMENT
fq=class:Blog.BlogPostClass
qf=object.Blog.BlogPostClass
The main difference:
- it was "__INPUT__*" query string and
- (as far as I understood) it is "__INPUT__" if parameter "q" is
omitted
The result is Solr Suggest changes it's behaviour and gives only exact results.
To make Search Suggest running as it was, we have to add: "q=__INPUT__*"
Is it done by puprpose or it is a bug and I have
to "jira" it?
On purpose. I did it as part of
http://jira.xwiki.org/browse/XWIKI-10051 (check the documentation
links). The reason I dropped the * (star) is because:
(1) Prefix matching is costly
(2) The search suggest is not a filter (in the sense that you have a
list of item and you type some text and it filters the items starting
with that text). Search is more complex. The search text is analysed,
stop words are removed, etc.
As you said, you can get back the previous behaviour using "q=__INPUT__*"
Let me know what yo think,
Marius
>
>
> Kind regards,
>
> Dmitry
> _______________________________________________
> users mailing list
> users(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users