Thanks-you Erik and Incze. I now understand the issue and I'm trying to create a
"KeywordAnalyzer" as suggested from you book excerpt, Erik:
http://issues.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=6727
However, not being all that familiar with the Analyzer framework, I'm not sure how to
implement the "KeywordAnalyzer" even though it might be "trivial" :) Any hints, code,
or messages to look at?
<<from message link above>>
Ok, here is the section from Lucene in Action. I'll leave the
development of KeywordAnalyzer as an exercise for the reader (although
its implementation is trivial, one of the simplest analyzers possible -
only emit one token of the entire contents). I hope this helps.
Erik
>>
thanks again,
chad.
-----Original Message-----
From: Incze Lajos [mailto:[EMAIL PROTECTED]
Sent: Tue 3/23/2004 8:08 PM
To: Lucene Users List
Cc:
Subject: Re: Query syntax on Keyword field question
On Tue, Mar 23, 2004 at 08:10:15PM -0500, Erik Hatcher wrote:
> QueryParser and Field.Keyword fields are a strange mix. For some
> background, check the archives as this has been covered pretty
> extensively.
>
> A quick answer is yes you can use MFQP and QP with keyword fields,
> however you need to be careful which analyzer you use.
> PerFieldAnalyzerWrapper is a good solution - you'll just need to use an
> analyzer for your keyword field which simply tokenizes the whole string
> as one chunk. Perhaps such an analyzer should be made part of the
> core?
>
> Erik
I've implemented suche an analyzer but it's only partial solution
if your keyword field contains spaces, as the QP would split
the query, e.g.:
NOTTOKNIZED:(term with spaces*)
would give you no hit even with an not tokenized field
"term with spaces and other useful things". The full solution
would be to be able to tell the QP not to split at spaces,
either by 'do not split till apos' syntax, or by the good ol'
backslash: do\ not\ notice\ these\ spaces.
incze
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
