[
https://issues.apache.org/jira/browse/JSPWIKI-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18137364#comment-18137364
]
Arturo Bernal commented on JSPWIKI-1321:
----------------------------------------
Ulf, pull request 575 is meant to cover what you asked for in the review of
pull request 543. With a page named Weblog_blogentry_021126_1, name:blog*26 and
name:entry*26* now find it in my tests, and the relevance is scaled so that the
best result is 100. A search that only ends in *, such as name:man* or
name:entry*, still starts at the beginning of a word, so name:entry* does not
find that page.
I have only tested it with automated tests and an in-memory index, not on a
wiki with the Weblog plugin. Could you try it there and tell me whether it does
what you expected? In particular: do name:blog*26 and name:entry*26* find the
pages you expect, do the relevance bars look right, and should a search like
name:entry* also find pages whose word only contains entry?
> Wildcards in the middle of a search term do not match inside the words of a
> page name, and the relevance goes above 100
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JSPWIKI-1321
> URL: https://issues.apache.org/jira/browse/JSPWIKI-1321
> Project: JSPWiki
> Issue Type: Improvement
> Reporter: Arturo Bernal
> Priority: Minor
> Labels: pull-request-available
>
> Follow-up of JSPWIKI-501 (pull request 543), from the review of Ulf Dittmer.
> For a page named Weblog_blogentry_021126_1, the provider indexes in the field
> name the tokens weblog, blogentry_021126_1, weblog, blogentry, 021126 and 1
> (measured with ClassicAnalyzer on the text the provider builds for that
> field). A wildcard term is matched inside one token. Measured on an in-memory
> index with seven page names, with the behaviour of master and of the branch
> of pull request 543:
> * name:blog*26 finds nothing
> * name:entry*26* finds nothing
> * name:man* finds only Man_Page, not Human_Page or Woman_Page
> The reviewer expects the first two to find the page, and said that
> name:blog*26 finding nothing while name:blog*26* finds pages is unexpected.
> A second point from the same review: the relevance of a result is the Lucene
> score multiplied by 100 with no maximum, so values above 100 appear (108 and
> 255 were measured on the branch of pull request 543). The reviewer suggested
> scaling it to 0-100 or leaving it out.
> Not measured yet: the effect on searches in the page contents, and the cost
> of terms that begin with a wildcard.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
