Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <4FF2A732.30109@codemium.com>
Date: Tue, 03 Jul 2012 10:02:58 +0200
From: thomas <thomas@codemium.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
 rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: solr-user@lucene.apache.org
Subject: Near Real Time Indexing and Searching with solr 3.6
Content-Type: multipart/alternative;
 boundary="------------060309040408020404000306"

--------------060309040408020404000306
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

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


--------------060309040408020404000306--