Geek Answers Handbook

How far is the original Lucene.Net?

I noticed that Lucene recently released v2.9 (September 25 this year - 2009), while Lucene.Net seems to be v2.0 (released in 2007):

  • Does v2.0 Lucene.net match the features found in version 2.0 of the original Apache Lucene
  • Have improvements been made to Apache Lucene since 2007 to guarantee the use of the Java version (with some interactions)?
+6
lucene
source share
3 answers

Version numbers correspond to Java and .Net versions - the .Net version is the direct port of the Java version (so yes, the functions in version 2.0 of Lucene.net correspond to the functions found in version 2.0 of the original Apache Lucene).

Later versions are available than v2.0 Lucene.Net. The Lucene.Net user list recently announced that port v2.9 is under development and will be ready for testing soon. I am using Lucene.Net v2.3.2 (which was released on July 24, 2009) in a production application without any problems. There is also a later v2.4, which was released on August 19, 2009.

The Lucene.Net project page has a full list of releases.

+6
source share

They have much more recent builds in SVN repositories. For all the basic things, I think it works very well. I am sure that in corner cases, the latest JAVA circumvent this, but for basic things you should be fine.

Look here

+2
source share

It depends on your project requirements and overall architecture. Lucene, as you know, is a class library, not a separate service, so you'll probably write code that uses the lucene library in either .NET (C #) or Java. If the rest of your project is .NET, then it might make sense to use the Lucene.NET port, even if it's behind a Java version. On the other hand, if you need the very general functionality of Lucene, you can use SOLR as a standalone service, and then use web services to interact with Lucene from your other components, such as .NET services, website interfaces, etc. d. The difference between the versions of Lucene.NET and Java is small, basically some performance improvements and some corrections / changes in range requests, as well as support for a larger load, but basically these are advanced features that you might not need. We use Lucene.NET 1.9 and it is very stable and very fast for us. We have over 200 million documents distributed across 8 indices.

0
source share

More articles:


All Articles