Two of the features I've been looking forward to and am now testing are numeric fields, which provide significant performance improvements on numeric range queries, and the underlying change to per-segment searching and caching. The latter sounds rather innocuous at first glance, but when coupled with a custom merge policy can improve heap utilization for large indexes.
You can certainly build your application against 2.4 and then migrate to 2.9 at a later time if you are under time constraints to deliver something quickly. Michael -----Original Message----- From: Markus Wolters [mailto:mar...@naxma.com] Sent: Tuesday, December 08, 2009 1:24 PM To: lucene-net-user@incubator.apache.org Subject: AW: Safe to use Release 2.9.1 Beta for production? Thanks for your advice. Are there any mature features I might miss when using version 2.4.0? Markus -----Ursprüngliche Nachricht----- Von: x...@mail.ru [mailto:x...@mail.ru] Gesendet: Dienstag, 8. Dezember 2009 18:23 An: lucene-net-user@incubator.apache.org Betreff: Re: Safe to use Release 2.9.1 Beta for production? I would not recommend use 2.9.1 in the production right now (it may be ok, but may not). It is safer to use 2.4.0. --- Andrei Markus Wolters wrote: > Hi @all, > > > > I'm new to Lucene(.NET) and want to include it into my current ASP.NET > project I'm working on to support fuzzy full-text searches. > > > > I am unsure which version to use. Is it safe already to use the /trunk > version, which is 2.9.1 Beta right now? Or should I better use the tag > 2.4.0? I need special querys including spatial data, so I thought the > latest versions would be a good starting point... > > > > Anyways, keep up the good work! > > > > I did some comparison to Sphinx and Xapian, but I think at least for me, > Lucene is the right way to go. > > > > Cheers, > > Markus > > > > >
