lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik Hatcher <e...@ehatchersolutions.com>
Subject Re: implementing a TokenFilter for aliases
Date Fri, 05 Dec 2003 17:22:32 GMT
On Friday, December 5, 2003, at 11:59  AM, Allen Atamer wrote:
> Below are the results of a debug run on the piece of text that I want
> aliased. The token "spitline" must be recognized as "splitline" i.e. 
> when I
> do a search for "splitline", this record will come up.
>
> 1: [173] , start:1, end:2
> 1: [missing] , start:1, end:6
> 2: [hardware] , start:9, end:7
> 3: [for] , start:18, end:2
> 4: [bypass] , start:22, end:5
> 5: [spitline] , start:29, end:37
>
> I also added extra debug info after the token text, which are the
> startOffset, and the endOffset. Lucene has the first token "173" only
> stored, it is not indexed. The remaining terms are tokenized, indexed 
> and
> stored. Does this make a difference?

I don't understand what you mean by "173" - is that output from a 
different string being analyzed?

Well, it's obvious from this output that you cannot find "spitline" 
when "splitline" is used in a search.  Your analyzer isn't working as 
you expect, I'm guessing.

	Erik


---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org


Mime
View raw message