> Thanks for the reply, but I am using the same analyzer
> for the index, as I am for the searching. So, I don't
> think that is my problem.
>
> Let me try and explain the problem more clearly...
>
> I have this query
>
> contents:product
>
> That is, I want to search the field "contents" for the
> term 'product'.
>
> The porter stemmer filter parses this and produces
> these tokens
>
> content
> product
>
> But since the field was stored as "contents", that is
> Field.Text("contents","product") and the Field class
> does not analyze the key of a Field, it does not find
> a match.
Ah, different story. The good news is that the new query parser (the
one I wrote last week) doesn't have this defect. This was definitely
a bug in the old query parser.
Try upgrading to the latest version from CVS and see if that makes
your problem go away.
_______________________________________________
Lucene-users mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/lucene-users
