Simon Willnauer <simon.willna...@googlemail.com> wrote: > Hey Bill, > let me clarify what Version is used for since I think that caused > little confusion.
Thanks. > The Version constant was mainly introduced to help > users with backwards compatibility and upgrading their codebase to a > new version of lucene without breaking existing applications / indexes > build with previous versions. For instance StandardAnalyzer preserves > the positionIncrement in its StopFilter which was introduces in Lucene > 2.9. If you use 2.4 and upgrade to 2.9 this change might break you app > since you indexed with a 2.4 behavior. You phrasequeries might not > work as expected anymore. If you don't have any upgrade issues or if > you can simply reindex you might just use the latest version. That's what I'm trying to do. But how? LUCENE_CURRENT is deprecated! How about adding a constructor for StandardAnalyzer that takes no parameters and is implicitly LUCENE_CURRENT? > Some usecases might require somewhat "buggy" behavior which has been > fixed in various places in lucene but must be maintained because of > backwards compatibility this is also done by Version. Sure. > If a certain > class like IndexWriter / IndexReader have maintained compatibility > without a Version constant so there is no need to pass it to them. You > will be implicitly on the latest version. Good. Bill --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
