My feeling is that real-time search first has to make it into Lucene. Once that is done we can add support for it in Solr.
My feeling is also that there are 2 different and parallel efforts going on for adding real-time search to Lucene, but that's a topic for the Lucene dev ML. Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch ----- Original Message ---- > From: Jason Rutherglen <[EMAIL PROTECTED]> > To: solr-user@lucene.apache.org > Sent: Saturday, September 27, 2008 11:31:14 AM > Subject: Re: Anyproblem in running two solr instances on the same machine > using the same directory ? > > The question I have is what is the optimal approach for integrating > realtime into SOLR? What classes should be extended or created? > > On Sat, Sep 27, 2008 at 9:40 AM, Otis Gospodnetic > wrote: > > Solr today is not suited for real-time search (seeing newly added docs in > search results as soon as they've been added - the way databases work, for > example). Work on that is in progress, though. > > > > > > Otis -- > > Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch > > > > > > > > ----- Original Message ---- > >> From: Jagadish Rath > >> To: solr-user@lucene.apache.org > >> Sent: Saturday, September 27, 2008 6:24:02 AM > >> Subject: Re: Anyproblem in running two solr instances on the same machine > using the same directory ? > >> > >> I am indexing data provided by the users our web site. If load on the site > >> increases, the rate of the commits also increases. The nature of the data > >> is > >> such that it should get reflected in the index instantaneously. > >> > >> On Sat, Sep 27, 2008 at 4:00 AM, Yonik Seeley wrote: > >> > >> > On Fri, Sep 26, 2008 at 2:18 AM, Jagadish Rath wrote: > >> > > - *What are the other solutions to the problem of > >> > > "maxWarmingSearchers > >> > > limit exceeded error " ?** * > >> > > >> > Don't commit so rapidly? > >> > What is the reason for your high commit rate? > >> > > >> > -Yonik > >> > > > > >
