On Tue, May 19, 2009 at 6:56 AM, DM Smith <dmsmith...@gmail.com> wrote:
> I really like the idea of a settings class. Another benefit, *especially if > it is documented well*, user's would be led to tuning parameters. > > In this settings class, would there be setters/getters so that one could > take particular defaults and tweak them? E.g. I like one default from 2.4 > but will take everything else from 3.0. Therefore, I use the 3.0 defaults, > but change one of the settings to match 2.4, as in: > > LuceneSettings myDefaults = LuceneSettings.defaults3_0(); > myDefaults.setXXX(LuceneSettings.defaults2_4().getXXX()); > LuceneSettings.useDefaults(myDefaults); Exactly -- one could start from SettingsMatchin24 and then cherry-pick the 2.9 improvements a-la-cart. And I agree on documentation: the settings should make it clear what they do, what the default was in 2.4, why the default was changed in 2.9 (what the benefit/tradeoffs were), etc. But we need to get this in for 2.9, so that starting w/ 3.x we are free. Mike --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
