Michael McCandless wrote:
Or, the removal of StopFilter as "Standard" all together. This coupled with
a QP that created phrases around stop words is a better solution.
Interesting... that'd be a pretty big change to StandardAnalyzer,
though.
I can see we are spinning off lots of neat ideas, decoupled from the
"Settings" proposal, here :)
For instance, if we removed the StopFilter from the StandardAnalyzer, then
what? A Settings object would not be able to account for it.
Why not? The settings object could have say a property
"analysis.standard.enableStopFilter"?
I think this is a great idea down the road. We shouldn't be removing
stopwords by default, and we should have better query time stopword
removal. It won't help out of the box performance, but it will help
first time users get stopwords right, rather than pointing them down the
wrong path to start as we do now.
- Mark
--
- Mark
http://www.lucidimagination.com
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
