lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From karl wettin <ka...@snigel.net>
Subject Re: IndexUpdateListener
Date Sat, 27 May 2006 08:37:35 GMT
On Sun, 2006-05-14 at 22:32 -0400, Erik Hatcher wrote:
> 
> On May 14, 2006, at 1:48 PM, karl wettin wrote:
> >> An app using Lucene still needs to coordinate all the activity
> >> surrounding IndexReaders and IndexWriters, including explicit  
> >> closure, so the app will know anyway when the index has changed, 
> >> right?
> >
> > A car could go 600 miles in reverse, but I'd prefere not. :)
> 
> Right, so what Yonik is saying is Solr implements most (if not all)  
> of your needs in this regard right now.  It is a working  
> implementation of your stated end goals, but it is at a different  
> layer than you'd like....
> 
> >
> >> (unless you are talking about adding the callbacks to 
> >> IndexModifier)
> >
> > As deep as possible.
> >
> > All the user would need to know is Directory.getListerners()
> 
> At this point we have to stop speculating and someone implement this  
> in their local version of Lucene with performance profiling before  
> and after listeners are added and ensure that we don't slow Lucene  
> down with such things and then contribute the code along with use and
> test cases. 

As always no test cases, but the results is a couple of decorators on
reader & writer that keeps track of what is going on. It would be
possible to add hooks further down the rabbit hole:

http://issues.apache.org/jira/browse/LUCENE-581


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org


Mime
View raw message