Mailing-List: contact jspwiki-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jspwiki-user@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of juanpablo.santos@gmail.com
 designates 209.85.214.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <51446A6D.7050606@davekoelmeyer.co.nz>
References: <5128AD8F.5050705@davekoelmeyer.co.nz>
	<CAEUnRMsG0cN1ucoHwTYT+jU_wECf15HibwuaGOHwo_11yBZD-w@mail.gmail.com>
	<5129C71F.4080301@davekoelmeyer.co.nz>
	<CAEUnRMsQ2Q7OPyRkRBVQr_MLpzrO2TSJNjz9-FQ_FrRJ=WEGQQ@mail.gmail.com>
	<513ADB43.7020408@davekoelmeyer.co.nz>
	<CAMufup5wA+VRDJjOfwWoNtd=M4GVy4=WZDCaJe0s5N41ZoyJvg@mail.gmail.com>
	<51430A58.2090106@davekoelmeyer.co.nz>
	<51446A6D.7050606@davekoelmeyer.co.nz>
Date: Sat, 16 Mar 2013 14:53:23 +0100
Message-ID: 
 <CAMufup5HLQx97fEMx_WtPwAapUcrQH_vfW=yZhO192hUrQsPOQ@mail.gmail.com>
Subject: Re: Quick search has stopped working
From: =?UTF-8?Q?Juan_Pablo_Santos_Rodr=C3=ADguez?=
 <juanpablo.santos@gmail.com>
To: jspwiki-user@incubator.apache.org
Content-Type: multipart/alternative; boundary=bcaec54ee608516d9704d80b14d1

--bcaec54ee608516d9704d80b14d1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Dave,

could you try switching the StandardAnalyzer to
org.apache.lucene.analysis.standard.ClassicAnalyzer? from the javadocs
"ClassicAnalyzer was named StandardAnalyzer in Lucene versions prior to
3.1. As of 3.1,
StandardAnalyzer<http://lucene.apache.org/core/3_6_0/api/core/org/apache/lu=
cene/analysis/standard/StandardAnalyzer.html>implements
Unicode text segmentation, as specified by UAX#29" so maybe that
could explain the search differences between versions

I'm unable to look at this right now, but I'll try to do it next week


br,
juan pablo

On Sat, Mar 16, 2013 at 1:49 PM, Dave Koelmeyer <
dave.koelmeyer@davekoelmeyer.co.nz> wrote:

> On 16/03/13 12:47 AM, Dave Koelmeyer wrote:
>
>> On 13/03/13 08:56 AM, Juan Pablo Santos Rodr=C3=ADguez wrote:
>>
>>>
>>> Lucene was updated from 2.0.0 to 3.6.0 in 2.9.0-svn-3 (
>>> https://issues.apache.org/**jira/browse/JSPWIKI-729<https://issues.apac=
he.org/jira/browse/JSPWIKI-729>),
>>> and the code rewritten
>>> to use the new API, but essentially it has the same behaviour as before=
,
>>> it
>>> passes the same unit tests. Could you please set the logger level to
>>> debug
>>> to see if something pops out from the log file?
>>>
>>> I'm assuming you're using the LuceneSearchProvider in your
>>> jspwiki.properties and the StandardAnalyzer (these are the default
>>> values)
>>>
>>>
>> Thanks for the reply, I will do that and post any relevant output
>> shortly. Just for information I have created a second GlassFish domain
>> using the same host OS, GlassFish and Java versions, but using JSPWiki
>> 2.8.3. Pointing JSPWiki 2.8.3 to a copy of the same content repository u=
sed
>> with JSPWiki 2.9.0 and performing a search I get the expected number of
>> quick search results. Contrary to what I said in my original post on thi=
s
>> topic I may well have first observed the behaviour after upgrading to 2.=
9.0.
>>
>>
> Hi All,
>
> Well I've enabled debug output (according to http://doc.jspwiki.org/2.4/*=
*
> wiki/JSPWiki.properties#**section-JSPWiki.properties-**
> TurningOnFullDEBUGMode<http://doc.jspwiki.org/2.4/wiki/JSPWiki.properties=
#section-JSPWiki.properties-TurningOnFullDEBUGMode>) and I can't see anythi=
ng error-wise in either the GlassFish or JSPWiki
> log files, certainly not anything related to search or Lucene. I've got a=
ll
> Lucene and search values at defaults in jspwiki.properties too, to answer
> your question.
>
> Any other pointers to things to check for? And has anyone else perhaps
> done an A/B test between JSPWiki 2.9.0 and earlier versions?
>
>
> Cheers,
> Dave
>
> --
> Dave Koelmeyer
> http://blog.davekoelmeyer.co.**nz <http://blog.davekoelmeyer.co.nz>
>
>

--bcaec54ee608516d9704d80b14d1--