|WikiProject Java||(Rated Start-class, Low-importance)|
|WikiProject Computing||(Rated Start-class)|
|The content of Kinosearch was merged into Lucene. That page now redirects here. For the contribution history and old versions of the redirected page, please see . (24 April 2014)|
--Rkthorne 03:10, 6 September 2005 (UTC) Have updated the latest Lucene implementations.
Nutch Lucene based or not?
Ported vs bindings
I don't know the product, but I think it was not ported to so many different programming languages. I expect it to have bindings for those languages? I have the same feeling. Notably, I did not find a native C++ implementation. —Preceding unsigned comment added by 18.104.22.168 (talk) 10:49, 2 August 2008 (UTC)
At least the PHP port is definitely a stand alone implementation. It uses the same index format, but runs without using any Java code. —Preceding unsigned comment added by 22.214.171.124 (talk) 09:57, 24 February 2009 (UTC)
How Indexing Done In Lucene
How Indexing Takes Place In Lucene
How to index images of text pages
Lucene -> Lucene Java
"Lucene" is the name of the Apache Top Level Project (TLP) which serves as an umbrella for dealing with all search related apache subprojects -- including "Lucene-Java", a java search library used as the foundation for some of the other sub projects (Nutch and Solr) and the reference implementation for some of the "port" subprojects (Lucene.Net and the now defunct Lucene4c). Some subprojects however have no direct relationship to the "Lucene Java" library, but are still included in the Lucene TLP because they are search related and share common goals and communities (Hadoop and Lucy)
In a broad discussion/context of user communities or Apache projects the term "Lucene" refers to the TLP and "Lucene-Java" (or "Java Lucene") refers to the specific sub project. Within the Lucene community (or any of the sub communities), "Lucene" is frequently used to refer to the Lucene-Java project/product as long as the context is clear.
--hossman 05:10, 28 June 2007 (UTC)
Java versus C#: Since the code is so similar, comparing the performance on the different virtual machines would make for a very interesting comparison between Java and C#.
I don't think this article answers the "What is it?" question in the first (or second) sentence. It does not happen before in the second section, "Features and common use":
"... full text indexing and searching ..."
What do you think?