> Jason Rutherglen wrote:
> I took a look at Jackrabbit, which are a very cool animal,
:-)
> and there are similar ideas in the Lucene portion. I will
> try to take a look at the source to get a better understanding.
The Jackrabbit indexing code is pretty much tied to Jackrabbit and
jsr-1
If you are looking for another example along the same principals,
(but considerably less sophisticated :) ), see
https://source.sakaiproject.org/svn//search/trunk/search-impl/
This manages a queue of change events on items to be indexed, that
queue is processed by a cluster of search indexer
I took a look at Jackrabbit, which are a very cool animal, and there are
similar ideas in the Lucene portion. I will try to take a look at the
source to get a better understanding.
On Fri, Jul 11, 2008 at 9:09 AM, Ard Schrijvers <[EMAIL PROTECTED]>
wrote:
> Hello Jason et al,
>
> Indeed there ar
11 jul 2008 kl. 14.29 skrev Jason Rutherglen:
Karl, does this answer your question or are there areas that could
use more explanation?
That's good stuff, you should add it to the docs.
karl
-
To unsubscribe, e-mai
Hello Jason et al,
Indeed there are plenty of usecases of instantly needed updated
searches, for example the jsr-170 (jcr) compliant Jackrabbit
implementation: it havily relies on lucene for searching and hierarchy
resolving, and according jsr-170 spec after a save(), changes need to be
visible in
I started a wiki name at
http://wiki.apache.org/lucene-java/OceanRealtimeSearch linked from
http://wiki.apache.org/lucene-java/LuceneResources.
Perhaps I should add some background on the wiki. I can add a little bit
here. I was an early Solr developer/user at a social networking company
when Go
10 jul 2008 kl. 22.08 skrev Jason Rutherglen:
Is there a good place to put Ocean https://issues.apache.org/jira/browse/LUCENE-1313
documentation? Is there a place on the wiki that is good?
Hi Janson,
the wiki is just fine.
I've been reading the docs and looked at your patch. There is a lo
