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

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

Commit 718925b1c9951292b193662ebdea154a94d6ce71 in jspwiki's branch 
refs/heads/dependabot/maven/org.codelibs-nekohtml-2.1.2 from Juan Pablo Santos 
Rodríguez
[ https://gitbox.apache.org/repos/asf?p=jspwiki.git;h=718925b1c ]

JSPWIKI-1171: Ensure Lucene indexes all pages and attachments, even when they 
don't fit in the cache


> Search not working on unmodified files
> --------------------------------------
>
>                 Key: JSPWIKI-1171
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-1171
>             Project: JSPWiki
>          Issue Type: Bug
>          Components: Search
>    Affects Versions: 2.11.1
>            Reporter: Andrew Ducker
>            Priority: Major
>         Attachments: JSPWikiException.txt
>
>
> Lots of pages aren't turning up in search.
> We cleared the lucene folder from the working directory, and it rebuilt it - 
> but quite quickly for 13,000 pages.  And the total size of the Lucene files 
> was around 2.5MB, which seemed far too small.
> Doing a search failed to bring back pages that had the given word in their 
> name and content.
> Editing one of those pages (adding a space) caused it to then appear in the 
> searches.
> Checking the logs I found a lot of errors in the form:
> [ERROR] 2022-04-12 15:50:17.274 [main] o.a.w.r.DefaultReferenceManager - 
> Error while trying to fetch a page name; trying to cope with the situation.
>  org.apache.wiki.api.exceptions.ProviderException: Illegal page name
> (See attachment for whole exception trace)
> Sadly, it doesn't tell me what the illegal page names are.
> This wiki has been upgraded from version 2.8 - are there compatibility issues 
> with page names there?



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to