lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shai Erera" <>
Subject Re: Potential bug in StandardTokenizerImpl
Date Tue, 27 Nov 2007 07:18:02 GMT
I understand it would change the behavior of existing search solutions,
however the current behavior is just wrong. An ACRONYM cannot be ABC.DEF. If
you look up acronym in Wikipedia, you find only examples of I.B.M. / U.S.A.
like, or NATO, IBM, USA, but nothing of the form StandardAnalyzer currently

There are several ways to solve this change:
1. Create a new analyzer that fixes the problem - that way, applications
that don't want to use it will not have to, if they feel ok with the current
behavior. However, for those who would like to get a correct behavior,
they'll be able to. This is not my favorite solution, but I think it would
be preferable than simply not fixing it.
2. Fix it in the new version (2.3) and specifically mention that in the
release notes. Aren't there releases where applications need to re-build the
index because of fundamental changes?

Am I the only one who thinks that?

BTW, I changed the definition in the jflex file and recompiled using jflex
and it indeed solved the problem. It now recognizes and as hosts. I can attach the 'patch' files if you'd like to

On Nov 27, 2007 9:07 AM, Chris Hostetter <> wrote:

> : If you pass "", the output is (,0,11,type=<HOST>)
> : (which is correct in my opinion).
> : However, if you pass "" (notice the extra '.' at the end),
> the
> : output is (wwwabccom,0,12,type=<ACRONYM>).
> see also...
> one hitch which potentially changing this now is that it would break
> some searches in applications that have existing indexes built using
> previous versions.
> -Hoss
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:


Shai Erera

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message