Such an analyzer already exists, in Lucene's Subversion repository,
under contrib/analyzers/: KeywordAnalyzer.
Robert Watkins wrote:
One approach for matching your queries with Luke would be to write a
custom Analyzer that does absolutely nothing to the terms. Then, if you
put this Analyzer in
One approach for matching your queries with Luke would be to write a
custom Analyzer that does absolutely nothing to the terms. Then, if you
put this Analyzer in your classpath when running Luke you can select it
as the Analyzer you want Luke to use to tokenize your query. This is
not, of course,
One approach for matching your queries with Luke would be to write a
custom Analyzer that does absolutely nothing to the terms. Then, if you
put this Analyzer in your classpath when running Luke you can select it
as the Analyzer you want Luke to use to tokenize your query. This is
not, of course,
On Thu, 2005-10-27 at 16:35 -0400, Sharma, Siddharth wrote:
> My index has 4 keyword fields and one unindexed field.
> I want to search by the 4 keyword fields and return the one unindexed field.
>
> I can iterate over the documents via Luke.
> But when I search for the same values that I see via
I figured out the problem when I copied the document from the clipboard.
It had trailing spaces.
After I changed the database query to have an ltrim(rtrim(
for each query, prior to indexing, its fine now.
-Original Message-
From: Sharma, Siddharth
Sent: Thursday, October 27, 2005 4:35 P
