Dave, can you test with 2.9.1-svn-30, that should have fixed the issue.
regards, Harry On 17 March 2013 15:34, Harry Metske <[email protected]> wrote: > in the 2.9 wiki, the maximum number of hits you get is 3, no matter what > you are searching for. > I have to dig a bit deeper, but the MAX_FRAGMENTS also has the value of 3 . > > regards, > Harry > > > On 17 March 2013 15:19, Harry Metske <[email protected]> wrote: > >> I have setup two test wiki's from scratch, a 2.8 and a 2.9. (both running >> in the same tomcat 7.0.37 instance with openjdk 1.7.0_15). >> >> I dumped my personal (250 page) wiki content into both of them, and did >> some random searches on both. >> Simply searching for the word "file" gives completely different results >> (68 versus 3 hits). >> This must be something with the new Lucene I guess. >> >> Can you file a JIRA issue on this ?, we have to investigate this further. >> >> kind regards, >> Harry >> >> >> On 17 March 2013 12:41, Dave Koelmeyer < >> [email protected]> wrote: >> >>> On 18/03/13 12:29 AM, Florian Holeczek wrote: >>> >>>> Hi again, >>>> >>>> Thanks, but I've tried all this and there has been no change in >>>>> behaviour. Also, I've got two instances of JSPWiki running on the same >>>>> host >>>>> platform, and I'm not seeing this with JSPWiki 2.8.3. >>>>> >>>> >>>> which JDK version are you using? I remember the first Oracle JDK 7 had >>>> some overly aggressive optimization which caused Lucene not to work >>>> properly. >>>> Did you enable the debug logging before index rebuild? I'd expect to >>>> see some Exception which may then cause the index build to stop. >>>> >>> >>> Hi Florian, >>> >>> I'm on JDK 6 update 37. I'll erase the Lucene cache and have another >>> look at the logs - perhaps I missed something. >>> >>> >>> Cheers, >>> Dave >>> >>> -- >>> Dave Koelmeyer >>> http://blog.davekoelmeyer.co.**nz <http://blog.davekoelmeyer.co.nz> >>> >>> >> >
