Hi, You might want to take a look at Solr's trunk (very soon to be 4.0.0 alpha release), which already has a near-real-time solution (using Lucene's near-real-time APIs).
Lucene has NRTCachingDirectory (to use RAM for small / recently flushed segments), but I don't think Solr uses it yet. Mike McCandless http://blog.mikemccandless.com On Tue, Jul 3, 2012 at 4:02 AM, thomas <tho...@codemium.com> wrote: > Hi, > > As part of my bachelor thesis I'm trying to archive NRT with Solr 3.6. I've > came up with a basic concept and would be trilled if I could get some > feedback. > > The main idea is to use two different Indexes. One persistent on disc and > one in RAM. The plan is to route every added and modified document to the > RAMIndex (http://imgur.com/kLfUN). After a certain period of time, this > index would get cleared and the documents get added to the persistent Index. > > Some major problems I still have with this idea is: > - deletions of documents from documents in the persistent index > - having the same unique IDs in both the RAM index and persitent Index, as a > result of an updated document > - Merging search results to filter out old versions of updated documents > > Would such an idea be viable to persuit? > > Thanks for you time >
