Hi Cedric, There is a wiki page on NRT at: http://wiki.apache.org/lucene-java/NearRealtimeSearch
Feel free tp ask questions if there's not enough information. -J On Mon, Oct 12, 2009 at 2:24 AM, melix <cedric.champ...@lingway.com> wrote: > > Hi, > > I'm going to replace an old reader/writer synchronization mechanism we had > implemented with the new near realtime search facilities in Lucene 2.9. > However, it's still a bit unclear on how to efficiently do it. > > Is the following implementation the good way to do achieve it ? The context > is concurrent read/writes on an index : > > 1. create a Directory instance > 2. create a writer on this directory > 3. on each write request, add document to the writer > 4. on each read request, > a. use writer.getReader() to obtain an up-to-date reader > b. create an IndexSearcher with that reader > c. perform Query > d. close IndexSearcher > 5. on application close > a. close writer > b. close directory > > While this seems to be ok, I'm really wondering about the performance of > opening a searcher for each request. I could introduce some kind of delay > and cache a searcher for some seconds, but I'm not sure it's the best thing > to do. > > Thanks, > > Cedric > > > -- > View this message in context: > http://www.nabble.com/Realtime-search-best-practices-tp25852756p25852756.html > Sent from the Lucene - Java Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
