Paul Libbrecht wrote:
I would really ove to apache SOLR to provide the possibility to tune finer the indexing and query process, thereby also enabling the extraction of a remote search server (keeping the plugin for the scheduling of updates and access to solr.
One of the features Vincent noted on Compass was the ability to do POJOs... I am not very convinced here since a normal xwiki application developer is actually doing... XOJOs and xwiki-lucene follows this rather well. In any cases, I've noted that solr supports indexing bean properties.
Among the bigger advantages is also that solr is a proven search tool in large industry projects, supports distribution and replication, as well as highlighting. It originated from CNET where it is still used.
In terms of API it's rather simpler than Lucene.
Between rewrite and updates, I would keep at least the queue and scheduling part which is pretty clean and useful to me.
I looked at SOLR a while back, and I didn't like it. Maybe I didn't see all the ways it can be used, so correct me if I'm wrong: it only works as a standalone webapp talking over HTTP. If that is the case, then I don't like that, since it implies conversion to XML and parsing back, opening HTTP connections, network transfer. And in the end it still gets to Lucene. Using Lucene internally involves just a simple method call. Much faster. -- Sergiu Dumitriu http://purl.org/net/sergiu/