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

ASF subversion and git services commented on JSPWIKI-1321:
----------------------------------------------------------

Commit 8ef26305a7092a62a3ac9292bbe31e95e5755ade in jspwiki's branch 
refs/heads/master from Arturo Bernal
[ https://gitbox.apache.org/repos/asf?p=jspwiki.git;h=8ef26305a ]

JSPWIKI-1321 Wait for all the pages to be indexed in the tests

The tests waited until the search found one page, and then compared the result
with all of them, so they could fail when the index was slow.


> A wildcard in the middle of a page name search term needs a * at its end to 
> find the 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)

Reply via email to