+1, too. I hate those modes. In my opinion, we should not have analyzers at all (just my personal opinion). "new Field(name, TokenStream)" is much enough from consistency standpoint!
----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -----Original Message----- > From: Robert Muir [mailto:rcm...@gmail.com] > Sent: Saturday, October 30, 2010 3:15 PM > To: dev@lucene.apache.org > Subject: Re: inconsistency/performance trap of empty terms > > On Sat, Oct 30, 2010 at 9:00 AM, Earwin Burrfoot <ear...@gmail.com> wrote: > > Speaking of consistency, I think NOT_ANALYZED is superfluous. Drop > > this mode, and it can be safely reproduced by a NotAnalyzingAnalyzer > > (insert better name here). > > > > +1. This is confusing and comes up often on the user list. > > The way I think it happens is like this: > Joe Schmoe, like a good user, just fires up StandardAnalyzer at both index and > query time. > Joe realizes he has a field that really shouldnt be tokenized, and sets it to > NOT_ANALYZED. > Joe is confused that queries dont work the way he should when he does this, > since its still analyzed by the queryparser with StandardAnalyzer. > > It would be far better to force him to use PerFieldAnalyzerWrapper + > NotAnalyzingAnalyzer or whatever, since then it would work intuitively. > besides, if he sets this NotAnalyzed, it actually goes thru 'analysis' > anyway: SingleTokenAttributeSource buried in the indexer. > And, in trunk, this means things like UTF-8 encoding are assumed, but really > this should be completely outside of the indexer. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional > commands, e-mail: dev-h...@lucene.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
