8 Apr
2009
8 Apr
'09
10:48 a.m.
Guillaume,
that is good news!
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.
paul
Le 07-avr.-09 à 21:49, Guillaume Lerouge a écrit :
I'm not able to answer your technical questions,
but I wanted to let
you
know that we plan on working on the Lucene plugin in an upcoming
release,
hopefully during the summer. We're not sure yet whether it's better to
rewrite the plugin or to make iterative improvements to the existing
one.
To sum up: there will soon (= in the coming months, not tomorrow
morning) be
active work on the plugin and any help & suggestions are welcome as
to what
is the best way to make it work optimally for XWiki :-)