Doesn't that one do just that - treats fields differently, based on
their name?
yes it does, but look at the question's title
How do I write my own Analyzer?
if someone has a problem with a non-tokenized field (which was the
problem of the mail thread that started this) then he doesn't know
I came accross the same problem and I think that the faq entry you
(Otis) propose should get a better title so that users can find more
easily an answer to this problem.
Correct me if I'm wrong (and please forgive any wrong assumptions I may
have made), put the problem is on how to query on a
: Problems with exact matces on non-tokenized fields...
lex Murzaku wrote:
I was trying this as well but now I get something I can't understand:
My query (Query: +element:POST +nr:3) is supposed to match only one
record. Indeed Lucene returns that record with the highest score but
it also returns
with exact matces on non-tokenized fields...
Hi, i have a problem with getting a exact match on a non-tokenized
field.
I have a Lucene Document with a field named element which is stored
and indexed but not tokenized. The value of the field is POST
(uppercase). But the only way i can match
PROTECTED]]
Sent: Thursday, September 26, 2002 8:22 AM
To: Lucene Users List
Subject: Re: Problems with exact matces on non-tokenized fields...
Hm.. a misunderstanding: i don't create the field with the value
POST? i create it with POST. element:POST? or element:POST* are
the strings i send
I have also observed this behavior.
- Original Message -
From: karl øie [EMAIL PROTECTED]
To: Lucene Users List [EMAIL PROTECTED]
Sent: Thursday, September 26, 2002 4:50 AM
Subject: Problems with exact matces on non-tokenized fields...
Hi, i have a problem with getting a exact match
Cutting [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 26, 2002 12:44 PM
To: Lucene Users List
Subject: Re: Problems with exact matces on non-tokenized fields...
karl øie wrote:
I have a Lucene Document with a field named element which is stored
and indexed but not tokenized. The value
