Hi, > >> 3) NumericField API is marked as experimental and volatile > >> (http://lucene.apache.org/java/3_0_1/api/core/index.html). Is there > >> any other "stable" API I can rely on in Lucene 3.0? If not, what > >> would be > > possible > >> NumericField replacement I could use now? > > > > "Experimental" in Lucene's API *only* means that the API (method > > signatures, > > classes) may change suddenly. The features are tested and working. > > My point was - I totally understand that a piece of API could have been made > deprecated and replaced with something else. That's the life we're living. > But would it not then make sense to replace it with something else which is > also reasonably stable (in terms of API)? > > Because developers aren't left with many options now - they have to convert > from using one API which is unavailable to another which is likely to change > rather sooner than later. It's just an early observation as historically Lucene > has been doing an amazing job in terms of API stability.
There are two problems: - You can go back to your old code and you don't need to move to NumericField at all. As noted before: The *replacement* for RangeQuery and ConstantScoreRangeQuery is TermRangeQuery. NumericRangeQuery is a new API and is totally different. If you use it, you have to get rid of old code and old way of use patterns - sorry :-) - 3.0 breaks backwards, so you cannot use any legacy-APIs anymore Uwe --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
